Otis Gospodnetic wrote:
It would be interesting to know _what_exactly_ uses your memory. Running under an optimizer should tell you that.I loaded it into a profiler a long time ago. Most of the code was due to Term classes being loaded into memory.
The only thing that comes to mind is... can't remember the details now,
but when the index is opened, I believe every 128th term is read into
memory. This, I believe, helps with index seeks at search time. I
wonder if this is what's using your memory. The number '128' can't be
modified just like that, but somebody (Julien?) has modified the code
in the past to make this variable. That's the only thing I can think
of right now and it may or may not be an idea in the right direction.
I might try to get some time to load it into a profiler on monday...
Kevin
--
Use Rojo (RSS/Atom aggregator). Visit http://rojo.com. Ask me for an invite! Also see irc.freenode.net #rojo if you want to chat.
Rojo is Hiring! - http://www.rojonetworks.com/JobsAtRojo.html
If you're interested in RSS, Weblogs, Social Networking, etc... then you should work for Rojo! If you recommend someone and we hire them you'll get a free iPod!
Kevin A. Burton, Location - San Francisco, CA
AIM/YIM - sfburtonator, Web - http://peerfear.org/
GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
