Re: Big push on testing needed

In message <554757c729bbailey@argonet.co.uk>
Brian <bbailey@argonet.co.uk> wrote:

>In article <3bc72c4755.DaveMeUK@my.inbox.com>,
> Dave Higton <dave@davehigton.me.uk> wrote:
>> Big news...
>
>> Current test (CI) builds are now release candidates. Yes, a new
>> release of NetSurf is imminent.
>
>> Please, everybody, download the latest test build (which will,
>> of course, change as bugs are found and fixed), give it a good
>> thrashing, and get your bug reports in.
>
>> Please also note that, since it's now close to release time, the
>> Javascript setting in Choices->Content is obeyed (and has been
>> for a couple of days or so now).
>
>> Dave
>
>Fetching websites seems to storm along at a rate of knots. Has something
>been done to NetSurf to enable this?

It has been suggested that the Unixlib fixes may be responsible.

If you go back far enough (before 2015 early November), the
regular expression parser was sometimes responsible for an
unbelievably high proportion of page load times. (At the
developer weekend last autumn, I saw an example where it took
90% of the CPU time.)

One other thing: the CI builds are coming out with logging
enabled. This will be changed for the release version. So,
if you want NS to go even faster, turn logging off (you'll
see the setting near the top of the !Run file). Of course:

1) you'll have to turn it back on again to get a log to report
a bug;

2) you'll want to turn it off again for each new CI version
you install.

It's a bit of an extreme example, but a Javascript test I
ran last night took over 6 minutes with logging enabled (it
created a 25 MB file) but 20 seconds with logging disabled.

Dave

____________________________________________________________
Can't remember your password? Do you need a strong and secure password?
Use Password manager! It stores your passwords & protects your account.
Check it out at http://mysecurelogon.com/manager