Performance Hints

On this page we'll collect some recommendations telling you how to configure nanoweb to get it to operate at highest speed possible.

HostnameLookups lead to some network traffic and delay time, so you probably want to disable this if you need more speed. Another good solution to skip this overhead for the server is to let the logger processes resolve the hostnames after the page already has been delivered; see HostnameLookupsBy for this / or you could completely skip this step and let some log file analyzing tool do these DNS lookups.

the libphp module is not faster than mod_cgi in general, it currently only seems to give you many disadvantages if used. It may be a bit more speedful than using the php cgi interpreter if your server load is _often_ very high.

using mod_rewrite generally slows down the server as it needs to re-read the .nwaccess/.htaccess files for every subdirectory files are requested from, and additionally the regular expressions are a real treat to server speed

the content negotiation method of mod_multiviews only comes into use if the requested file doesn't exists on the server, so the file search and regular expression matching shouldn't occur all the time and therefore doesn't slows down the serving process.
So most of the time it shouldn't be a performance problem using multiviews, when it is used only to select the primary html document.
However not specifying the filename extions in your <IMG>-tags and let the server select the appropriate one is probably a bad idea unless you don't serve different language variants of a picture (containing some rendered text of course!), multiviews cannot select the best variant out of GIFs and PNGs for example, because most browsers just request image/* (of any type) without telling wether they support any of the formats (-> thats why you should favour PNGs in general ;-).

mod_mysqllog should work on the same speed level as standard file or syslog logging, using the database one probably won't lead to more speed.