Hi all, following this thread
http://thread.gmane.org/gmane.comp.search.xapian.general/1922, now I can
sort my results by date, but the performance is very low (searches beetween
1~10 seconds), I want know if my problem is with Xapian or my
hardware+software, look:
Hardware (Not is a server, is a desktop (bad) adpted):
AMD Duron 1.5GHz - 64kb cache
900MB RAM (DDR 400)
2 HDs in the same IDE ( hda 40GB 7.200rpm, hdb 20GB 5.700rpm )
Software:
SO: Slackware 10.0.0
Postgresql-8.0.3 (228.384 rows to search)
Apache-2.0.53
Xapian-0.9.2 (228.384 rows to search)
Omega-0.9.2 -source was edited like thread, and without stemming
("none")-
Can someone help me?? Olly?? xD
Thanks a lot!
ps: Sorry about (bad) english
--
http://sdm.zapto.org/
--
Seja esperto, seja livre, seja Linux
Be smart, be free, be Linux
Soyez fut?, soyez libre, soyez Linux
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.tartarus.org/pipermail/xapian-discuss/attachments/20051218/c9688df7/attachment.htm
On Sun, Dec 18, 2005 at 04:23:03AM -0900, Rafael Jorge wrote:> Hi all, following this thread > http://thread.gmane.org/gmane.comp.search.xapian.general/1922Hmm, my option (b) in that thread isn't actually an option. I've replied to the thread with a correction for posterity.> now I can sort my results by date, but the performance is very low > (searches beetween 1~10 seconds), I want know if my problem is with > Xapian or my hardware+software, look:Hmm, it's not a large database (Gmane is using the same trick to implement "sort by date" on almost 30 million documents), and the hardware sounds reasonable. Some thoughts: You could try compacting the database (run it through quartzcompact). You could try using the new flint backend instead of quartz (flint databases can also be compacted with xapian-compact, but they do a better job of staying more compact in normal use so the gains are likely to be less): http://wiki.xapian.org/FlintBackend Also worth seeing if you're using $topterms in your query template (the default templates/query uses it currently though I'm wondering about removing it to a separate template). As currently implemented, calculating the topterms can be expensive on larger databases. Cheers, Olly