Reply restricted to "zodb-dev"... Adam Groszer wrote at 2007-3-14 12:58 +0100: >Currently we're looking at something based on catalog/indexes. >As I checked the most comfortable solution would be based on >hurry.query. >Some questions arose: >- Is it necessary/worth adding indexes on all attributes?
It is probably a good idea to index everything you want to search for. In our ZEO setup (with the ZEO client and the ZEO server on the same machine, i.e. a fast interconnection), fetching a single object from ZEO takes between 3 and 30 ms (depending whether the object is in the disk cache or need to be fetched from disk) with an average value of 4 to 5 ms. Thus, you do not want to fetch lots of objects.... >- How does the index perform on modification and retrieval? The usual data structures for indexes have logarithmic time complexity for insertion and (direct) lookup. Note however, that you may have large document list associated with some index terms. This may give you linear time complexity for most searches. "IncrementalSearch2" (togoether with "ManagableIndex") tries to avoid these linear time complexity (but can not always succeed) <http://www.dieter.handshake.de/pyprojects/zope> -- Dieter _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev