Caching of search result is not an option in the script.
How big is your set of index files. What hardware are you using? What script option are you using? What search times are you getting?
The normal CGI should be giving search times around 0.01 of a second to 0.5 seconds. So in most cases caching wouldn't have a significant impact, but would add complexity and use a lot of disk space, and run the risk of returning out of date results. Eventually, once a lot of words had been searched for, the cache would start to be inefficient compared to the main index. A user also won't notice the difference between 0.5 and 0.3 second of processing time.
Announcement
Collapse
No announcement yet.
Cache through ZOoM
Collapse
X
-
I want to cache the results. So that if somebody hits for same keyword then it should first check into the cache then the real results.
Leave a comment:
-
What sort of speeds are you getting, and with how many pages or unique words indexed? Our benchmark page should give you a fair idea of what's normal behaviour.
The CGI version gives very formidable performances up to the largest of indexes (half a million pages+). If you are really indexing data of this scale and magnitude, you should read this page for some helpful advice:
http://www.wrensoft.com/zoom/support...rge_sites.html
Towards the bottom of that page, there are details regarding bespoke search appliance solutions that we can offer, such as a FastCGI version which caches index data and improves speed significantly.
Leave a comment:
-
Cache through ZOoM
Hi,
How can we use the caching while searching with Zoom. Need to speed up the search.
Thanks In AdvanceTags: None
Leave a comment: