django haystack - Sharing Whoosh index -


i'm implementing cms site in django, , i'd add full-text content search. site reasonably small , generate low search traffic, think whoosh reasonable production solution.

my current understanding whoosh indexing , result generation happens in application process, rather requiring own daemon, great. however, i'm bit worried concurrent access index. can single whoosh index support reads (and potentially writes) multiple, uncoordinated processes? example, problematic if same index shared load-balanced django application servers, either in terms of serious performance degradation or index corruption?

thanks in advance advice.

it appears, based on whoosh documentation, possible share index between several threads/processes. docs on indexing here: http://packages.python.org/whoosh/indexing.html#indexing-documents indicate index locked writes when updating it, i'd imagine highly read-heavy application ok.


Comments

Popular posts from this blog

linux - Mailx and Gmail nss config dir -

c# - Is it possible to remove an existing registration from Autofac container builder? -

php - Mysql PK and FK char(36) vs int(10) -