The recent 0.9.1 release was the first to include the new Flint backend.
I've added a wiki page which documents it, including how to try it out:
http://wiki.xapian.org/FlintBackend
Oh yes, and we have a wiki! We have had for a while, but I finally got
around to making use of it...
Cheers,
Olly
Hi Olly, It looks good, but I have a few questions. First off, you talk about improved performance for adding documents, did this effort have any effect on updating (replacing) documents? I hope there isn't a more-than-marginal negative impact, since in our application we do more updates than additions (resp 631 vs 282 last night) where the updates are also with larger documents since they generally contain longer periods of discussions. Last nights run took about 31 minutes for indexing, so if that would've taken like 32 (or even 40) minutes with Flint, it'd be no problem at all though. Do you think the Flint backend will be better in terms of performance compared to (our setup with) a (zlib) compacted quartz database? Or is it too early in its development stage and should we wait a while for such things to become clear? As you know especially the position-table puts a lot of pressure on our machine, so significant improvements in that table are very interesting for us. Best regards, Arjen On 11-6-2005 3:44, Olly Betts wrote:> The recent 0.9.1 release was the first to include the new Flint backend. > > I've added a wiki page which documents it, including how to try it out: > > http://wiki.xapian.org/FlintBackend > > Oh yes, and we have a wiki! We have had for a while, but I finally got > around to making use of it... > > Cheers, > Olly > > _______________________________________________ > Xapian-discuss mailing list > Xapian-discuss@lists.xapian.org > http://lists.xapian.org/mailman/listinfo/xapian-discuss >
On Sat, Jun 11, 2005 at 02:44:58AM +0100, Olly Betts wrote:> The recent 0.9.1 release was the first to include the new Flint backend.Hmm, except I've just discovered that when apitest said it was running tests for flint, it was actually running them with a quartz database. Fixing that has revealed a couple of bugs in flint. One (failing to open a database for reading) is fixed. I working on the other right now (it's a bug in the interpolative coding of positionlists). Probably best to hold off trying Flint until I've got all the tests passing for real. Cheers, Olly
On 24-6-2005 9:19, Arjen van der Meijden wrote:> With a svn-snapshot of yesterday (0.9.1 - 6307) I get a error message > right away when doing that: > > acm@dev acm $ XAPIAN_PREFER_FLINT=1 XAPIAN_FLUSH_THRESHOLD=1000 > > copydatabase default-compact/ /var/omega/flint-normal > copydatabase: Item in value table is too large > > Of course it fits perfectly in the quartz tables, so that may be > something to look at? > Can I simply remove the value-table (and replace it with an empty file) > to test the other tables?It helps when I apply the zlib-patch... Copydatabase is running just fine to create a flint-version of our compacted database. Best regards, Arjen