netsurf: branch master updated. release/3.2-500-gd08acbc
chris.young at unsatisfactorysoftware.co.uk
Sun Nov 30 16:09:51 GMT 2014
On Sun, 30 Nov 2014 15:01:54 +0000, Vincent Sanders wrote:
> > (22.696681) content/llcache.c llcache_persist 2414: Wrote 884 bytes in 225ms bw:3928 http://aminet.net/pics/at.gif
> > (22.696759) content/llcache.c llcache_persist 2420: Overran timeslot
> > (22.696828) content/llcache.c llcache_persist 2426: Cannot write minimum bandwidth
> > (22.697699) amiga/misc.c ami_misc_req 51: Disc cache write bandwidth is too slow to be useful, disabling cache
> well under 4000 bytes a second is so slow that it is not useful.
> disc caching really needs to be several multiples of the network
> conenction speed to be useful. Although the minimum bandwidth setting
> is a passe din parameter and you can chnage the default value in
> desktop/netsurf.c to experiment.
I'll have a look at that.
> Is it possible that your implementation of a milisecond monotonic
> counter in libnsutils is problematic? If it is returning microseconds
> instead of miliseconds that would cause this erroneus behaviour.
I thought it might be wrong, so I rewrote it using a different timer.
I get very similar results to before.
When I return immediately, I'm still getting things like:
Wrote 94314 bytes in 1305ms
even though above it says:
Wrote 91944 bytes in 1ms
So there's something weird with the timer, or something slow is
happening between the timing interval.
I've just had a thought that some other task might be nicking the CPU
whilst the timing is happening - We're measuring how long it takes,
not how much CPU time it takes. Perhaps the monotonic timer should be
measuring CPU time for the task it's running under?
More information about the netsurf-dev