I found out that the preformance will get back in shape
(query time 1-2
secs)
around 10-20 mins after xapian DB updated.
So i guess this is the file system cache begins to build up.
Will start to clean up unnecessary unqiue terms and
continue to stack up more docs and see how it goes....
> First question, is this with quartz or flint? I'd
suggest using flint
> rather than quartz.
i was using quartz, now i will switch to flint, guess its
stable enough
while you suggeted =)
> Second question - does compacting the database help?
(Using quartzcompact
> for quartz, or xapian-compact for flint).
i never tried the compact utility yet, how to trigger this
function?
i cannot find it in the PHP wrapper... =/
>> Dev. Server:
>> INTEL p4 2.8 HT
>> 2G ram
>> 120G IDE 7200rpm 2M cache raid 1
>
> What's the operating system?
>
> Is it just the search running on this, or is there
anything else using
> it? If so, what else?
linux feodra
couple low traffic websites (apache / php/ mysql)
> I usually favour a "decoupled" design - fetch
and process your documents
> and dump them in batches to files in a spool directory.
Then an
> indexing process can sweep through the directory
periodically. The
> spool directory can be NFS mounted or copied over with
rsync or
> some other mechanism if you want to run processes on
different machines.
>
thx info
I was thinking of something like MOSIX http://www.mosix.cs.h
uji.ac.il/
but MOSIX seems a bit old and kinda discontinued....(not
sure)
Cheers n Merry Christmas
Andrey K
_______________________________________________
Xapian-discuss mailing list
Xapian-discuss lists.xapian.org
http://lists.xapian.org/mailman/listinfo/xapian-discuss
|