makedbz slow even with -s30000000

Alex Kiernan alexk at
Thu Jul 19 07:52:37 UTC 2001

Joe St Sauver <JOE at> writes:

> I am noticing slowness doing a makedbz with
> inn-CURRENT-20010718 even after specifying -s30000000 to 
> insure that the size of the database files is appropriately
> large. [By slow, I mean that the makedbz has been running 
> for roughly eight hours now...]

How much RAM is in the box?

> Interestingly/peculiarly, if I try makedbz -s 30000000
> (e.g., just add a space between the -s and the numeric argument),
> the command stops running almost immediately, reporting
> simply "Terminated" with no further diagnostic and a zero
> length history.n.hash and history.n.index (history.n.dir
> reads: 

That's weird. The code which handles that is just getopt & atol - what
platform are you running on?

> [One feature that would really be nice would be a periodic
> report about how close to completion things are getting...
> if, say, after eight hours, I knew I was 92% of the way 
> done, I'd be far more inclined to patiently let it run than
> if I was only 18% of the way down the road. (Normally I 
> don't care about completion-status graphs, but when we're
> talking HOURS, I *do* care...)]

I need to rewrite makedbz for the history API stuff, so I'll look at
something like that.

Alex Kiernan, Principal Engineer, Development, Thus PLC

More information about the inn-workers mailing list