On Wed, 2 Jul 2003 04:24, Neal Richter wrote: > It is possible to create two different environments for the > different DBs in the htdig classes that control them.
True, but the "_weakcmpr" database is internally created by mp_cmpr.c for any compressed database -- ht://Dig knows nothing about it. Of course, we could *change* the API to pass in two database environments (one for the database proper and one for _weakcmpr), but that is far from fixing it at the API level. > I am hesitant to put lots of time into tweaking BDB code > directly. > 2)BDB is a VERY widely used piece of software and it is > incredibly likely that most of the problems we encounter can be > fixed at the BDB API level in our classes. This of course excludes > our (Loic's) hacks to have ZLIB page compression. Yes, it is exactly Loic's code (mp_cmpr.c) that I was proposing to fix. In the past I hacked mp_alloc to try to work around the bug, but I had planned to back those changes out once b5 was out and there was time for a real fix. > The more we tweak the more we > diverge from stock BDB code and the more work we make for ourselves > long term. Agreed. > I used an STL hash and improved insertion time in the WordDB > considerably. Probably due to queing up all the inserts in larger > batches reduces overhead. That sounds impressive. OK -- I'll stop tinkering with the database code... Cheers :) Lachlan -- [EMAIL PROTECTED] ht://Dig developer DownUnder (http://www.htdig.org) ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ htdig-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/htdig-dev
