2 Feb 2006 15:09
Re: Last call for 2.4.3 problems
Ulrich Schmid <schmid <at> switch.ch>
2006-02-02 14:09:01 GMT
2006-02-02 14:09:01 GMT
on 27/1/06 21:08 Russ Allbery wrote: > Ulrich Schmid <schmid <at> switch.ch> writes: > > >>from the ChangeLog of 2.4.2 (missing in 2.4.3 ChangeLog): >>2004-06-02 20:11 hkehoe >> * history/hisv6/hisv6.c: In hisv6_reopen(), if MMAP_NEEDS_MSYNC and >> INND_DBZINCORE are set and nfsreader is false, override INCORE_NO >> to INCORE_MMAP > > >>2004-06-02 20:02 hkehoe >> * lib/dbz.c: Put msync call in putcore for INCORE_MMAP Move >> writethrough test from dbzsync to putcore because it only applies >> to INCORE_MEM > > >>whereas I assume that my problem is due to the changes in dbzsync / >>putcore. If I use in 2.4.3 dbzsync as of 2.4.1 I got the same history >>performance as with 2.4.1. Is the writethrough test correct in putcore? > > > Well, it's working for everyone else.... This is my timing from a box > running the 2.4.3 prerelease: > > INND timer: > Code region Time Pct Invoked Min(ms) Avg(ms) Max(ms) > article cancel 00:00:30.339 0.0% 2963 0.200 10.239 131.000 > article cleanup 00:03:46.943 0.3% 765822 0.260 0.296 0.506(Continue reading)
RSS Feed