Hi Alex and all,
I am coming out of a long discussion with some MySQL experts who believe that using persistent connections to MySQL is a very bad idea to do in an application that is on a server together with many other scripts. Each connection eats out lots of RAM and if it persists then very soon server will get overloaded and crash. There was strong recommendation that one refrains from using persistent connections unless for a heavy load server with very small number of databse driven sites.
I am still testing GM and so far have used it for personal mail but we are getting ready to release it and expect quite a good number of users. I am worried about that issue. For now GM will be hosted with other applications on a 700 MHZ PIII with 256 MB RAM. Do you believe I should run it without modperl? I have been told that 256 MB RAM will handle 50-60 simultaneous connections before it starts limping and if using persistent connections, this time will happen very quickly .
Please comment and advise
Thanks
Frank
I am coming out of a long discussion with some MySQL experts who believe that using persistent connections to MySQL is a very bad idea to do in an application that is on a server together with many other scripts. Each connection eats out lots of RAM and if it persists then very soon server will get overloaded and crash. There was strong recommendation that one refrains from using persistent connections unless for a heavy load server with very small number of databse driven sites.
I am still testing GM and so far have used it for personal mail but we are getting ready to release it and expect quite a good number of users. I am worried about that issue. For now GM will be hosted with other applications on a 700 MHZ PIII with 256 MB RAM. Do you believe I should run it without modperl? I have been told that 256 MB RAM will handle 50-60 simultaneous connections before it starts limping and if using persistent connections, this time will happen very quickly .
Please comment and advise
Thanks
Frank