On Fri, Apr 24, 2009 at 02:14:25PM +0200, oxy wrote: > I get it just by typing "mairix" in order to build my database.
Mairix keeps the database in memory when indexing, and it also memory-maps each file that it needs, resulting in a lot of memory use. Assuming you have enough memory to hold the database in memory, you might get better results if you split large mbox files into many small files and index them that way. Mairix does a final memory-map of the existing on-disk database when writing out the in-memory database, so if you already have a huge existing database in memory and another huge index on disk, your memory usage doubles right there. You can prevent that by removing your existing index before running mairix so that mairix doesn't try to map it. Your indexing is more likely to finish, but you'll have to index everything from scratch and you'll end up with something huge that mairix can't add to. -- | Ian! D. Allen - idal...@idallen.ca - Ottawa, Ontario, Canada | Home Page: http://idallen.com/ Contact Improv: http://contactimprov.ca/ | College professor (Open Source / Linux) via: http://teaching.idallen.com/ | Defend digital freedom: http://eff.org/ and have fun: http://fools.ca/ ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Mairix-users mailing list Mairix-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mairix-users
