Not sure if this is a bug or expected behavior.

I took Doug's suggestion and migrated to a large BUFFER_SIZE of 1024^2 . He mentioned that I might be able to squeeze 5-10% out of index merges this way.

I'm not sure if this is expected behavior but this requires a LOT of memory. Without this setting the VM only grows to about 200M ... As soon as I enable this my VM will go up to 1.5G and run out of memory (which is the max heap).

Our indexes aren't THAT big so I'm not sure if something's wrong here or if this is expected behavior.

If this is expected I'm not sure this is valuable. There are other uses for that memory... perhaps just doing the whole merge in memory...

Kevin

--

Please reply using PGP.

http://peerfear.org/pubkey.asc NewsMonster - http://www.newsmonster.org/
Kevin A. Burton, Location - San Francisco, CA, Cell - 415.595.9965
AIM/YIM - sfburtonator, Web - http://peerfear.org/
GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412
IRC - freenode.net #infoanarchy | #p2p-hackers | #newsmonster



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to