[Xapian-discuss] Xapian under 360 MB VPS

[Marlon Baculio]

Richard, thanks for the info on number of file handles per reader as well as the fact the readers won't cache anything. The OS caching sounds perfect for my needs. Thanks also for the tip on how I might compute the write threshold.

I'm used to multithreaded programming so I would tend to lean on that. I assume there are no file locking necessary in Xapian's read mode, or if there is, it's thread-safe? (I remember for Solaris, fcntl-based file locking doesn't work if you have multiple file descriptors to the same file from multiple threads (i.e. close() and lockf() don't mix). I did not encounter the same problem for Linux' flock() though.)

Also, to service lots of concurrent searches, the way to go (aside from throwing more hardware) is to increase number of processes/threads in the pool with their own reader as Xapian is not asynchronous. Is that correct?

(I might be prematurely optimizing here as I'm sure a $19 VPS hosting for 360MB will be a little tight for thousands of users, but I'm trying to get my money's worth :-)


--marlon