ZOOM Impact on the server

[TanujaK]

Hi:

Since we have installed ZOOM on the server and that while indexing the pages on the live server, there seems to be a large impact on other tasks/functions that are currently being run on the web server. Is there a way, we can reduce the impact and is there any other solution to index the website with out having the a large impact on the web server and its functionalities?

Thanks for your assistance in advance.

[David]

The indexing process can use a lot of RAM & bandwidth, plus a moderate amount of CPU activity and disk I/O. We have made a lot of changes in V5 to reduce this but some resource usage is unavoidable.

The more files you index the more resources you will use. The slower in the indexing process the longer the indexer will hold the half built index in RAM. But the faster indexing also means more of a spike in the CPU & disk load.

Further, the indexing activity also causes corresponding activity in the web server that serves the files (e.g. Disk I/O from the Apache web server).

Some suggestions.
1) Update the index less often
2) Schedule the index update to take place during low load periods on your server. e.g. 4am in the morning on a Sunday.
3) Move the indexer task to a different machine.
4) Study what is the bottle neck on your server. Maybe you just need a RAM upgrade?
5) Index less files if you can
6) Use incremental updates if it makes sense for you site
7) Study the load. Maybe the load is not from Zoom at all. Maybe it is from some script that dymanically generates your web site as the pages are hit by spiders.

[Ray]

Another option: have a dedicated/separate machine for indexing, which is locally networked to the live web server.