I'm sorry this post is a bit off-topic, but I think I should correct this. On Sep 4, 2008, at 11:54 AM, Oleg wrote: > Durus (and ZODB) has an index of all objects, the index is stored in > memory AFAIK - a real problem if one has millions of objects. Durus now has an option to store the index in the data file in a form that is usable directly from disk. With this option, the in-memory index is only for objects changed since the last pack. Durus works fine with millions of objects, as long as you don't have millions of rapidly-changing objects. I haven't used the Berkeley DB storage for Durus, but I'm pretty sure that the Durus/Python side of that would not use any in-memory index.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4