ccornell - OpenOffice.org wrote: > If anyone has any ideas or knowledge of this table in > MediaWiki, or in general with MySQL and can provide some insight here on > howw to fix this more permanently... or any other suggestions,
In addition to controlling the number of open connections to MySQL, introducing a reverse proxy server could help this situation. If the current system configuration is like this: Internet ---> Wiki server a proposal could be: Internet ---> reverse proxy server ---> Wiki server There are many reverse proxy server available. One of them might be Squid, http://www.squid-cache.org/ . Apache web server itself has it, too. Wiki pages are dynamically produced when a user request to browse it. In most cases, however, requests are a read-only access. Therefore, a result cache system could help this type of situation. MediaWiki is also capable of result cache, but it is implemented in collaboration with a back-end database server. If a reverse proxy server is introduced, slightly tuning both servers might be needed since from Wiki server's perspective of view, originating IP address is not a user's IP address but a reverse proxy server's one. The proxy server should append some extra HTTP headers describing a real IP address and the Wiki server should recognize them. Apache's reverse proxy module can do that. Squid, ... I am not sure. Regards, Tora --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
