Open GoogleCodeExporter opened 8 years ago
Seems fdatasync is harmful, since it is blocking operation.
Original comment by nuclear...@gmail.com
on 6 Mar 2010 at 9:02
Seems fdatasync is harmful, since it is blocking operation.
On some very loaded proxies it blocks squid with this patch.
posix_fadvise(fd, 0,0,POSIX_FADV_DONTNEED);
is almost useless without it, i will have to do more tests
Original comment by nuclear...@gmail.com
on 6 Mar 2010 at 9:05
Well, you're doing that on open and close - we could just throw that into the
AIO open/close handler.
i wonder why it's giving you a noticable improvement in performance. What made
you try it?
Original comment by adrian.c...@gmail.com
on 20 Mar 2010 at 8:47
I am not sure still in performance improvement. Real load changing... i will
try to
schedule more extensive testing in my cluster (4 with optimization, and 4
without).
Load is distributed over Linux Vserver, i can enable over roundrobin to make
similar
load.
Probably i must setup some data collection also to draw graphs...
Most significant improvements can be:
1)DONTNEED will release file from file cache. As i understand if file often
requested
- most probably it will be in squid own memory cache.
2)SEQUENTAL is able to turn more readahead. I'm not sure it will give any
benefit,
but if there is plenty ram for file caching it will make less seeks.
Original comment by nuclear...@gmail.com
on 20 Mar 2010 at 2:07
Original issue reported on code.google.com by
nuclear...@gmail.com
on 6 Mar 2010 at 8:18