[josiespencer]

Originally Posted by AndrewD

Is it really searches that are the problem?

That GET request is the request to download a document. It gets very cpu intensive, mainly because of the way (I think) you have set up the entries in your database - you're using full urls to point to the documents. The php code needed to access files in this way is expensive to execute - this is covered at length in the on line manual - even if the documents are actually on the same physical computer.

By far the best/cheapest way to handle the documents while making sure that the source is kept private is as follows:

- Use local_file_root and local_file_root_prefix to store documents on the same server but outside the web site directory structure
- Use local file names in the entries, not urls.

This can make 100 - 1000 fold improvement in cpu use.

If it's really searches that are causing the problem, I'll see how to help.

Yes, please, Andrew. I think it would be great if the Search on Links and Downloads could be disabled based on user group.