slow expire/expireover, 12/31/99 snapshot

Katsuhiro Kondou kondou at nec.co.jp
Thu Jan 6 22:31:01 UTC 2000


In article <4.2.2.20000105103134.00a404a0 at pop3.callatg.com>,
	Paul Theodoropoulos <paul at atgi.net> wrote;

} INSTALL, with a tablesize of 23017915, i should have enough ram to not have 
} to use tagged hash - yet it looks like i may need to.
} 
} am i reading the formula wrong, or is something perhaps fubar with my config?

When expiry, you have both current and new history dbz.
This means you need almost double size of its result.
INSTALL should be corrected at this point.

} (addendum, i just ran a brief truss on expireover, and noticed that it's 
} spewing a lot of the following, wondering if this is a problem or not:

Probably that truss shows getting new block, but
I don't have any idea why fcntl() fails like that.
-- 
Katsuhiro Kondou



More information about the inn-workers mailing list