In Reply To:
Just would like to know (from the traffic numbers), if that's really the case when very high traffic causes the problems or probably there is another kind of problem. Is your traffic secret?
Usually using normal cgi IMO at least 5-10 hits/sec should work fine, while using mod_perl at least 20-50 hits/sec may work fine. Again IMO. I have no experience with LSQL under very high traffic, so I can't estimate the performance LSQL can really handle. But at least we can see, if really reaches these limits or not.
Finally, definitely the more memory is better (if your server is swapping to disk a lot, you can achieve more performance by adding memory).
Would be fine to know how much memory needs each session for eg. 15.000 links. IMO, needs at least 10-20 Mb for each session, maybe more. On WinXP using about 2000 links, LSQL 2.1.1 memory usage is going up to 9.5Mb / session for page.cgi, dynamic mode, cgi execution (no mod perl).
So for 20 sessions per sec you need at least 200-300 Mb free memory, or more.
Hi,
Traffic really is the issue here. It's fine most of the time, but at peak times the server gets overloaded and we have angry emails coming in. Not good. In Alexa we're currently at about 15,000. So, not doing badly.
Following everyone's advice, we have decided to double the RAM to 1gb, up the processor, and install dual Mod-Perl and modproxy apache servers. Should work nicely.
Thanks for your help.
