If its a hosting PROVIDER, the table locking issue should really only be a factor for your database. If your design is good, then the rest shouldn't matter. Machine memory and processing power are another issue entirely. Other users could drag the machine down with poor design issues. One issue that we encountered, due to our own ignorance of course, was not allowing enough swap space for our mysql installation. We had 64MB of swap on a machine with 64MB of RAM. When we tried to process large queries the machine ran out of memory and crashed hard. Our short term work around was to take another, unused, partition and reformat it as swap. With 1.5 GB of swap, we never saw another problem, but we don't let users build their own databases either. -----Original Message----- From: mysql-digest-help [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 04, 2001 11:27 AM To: mysql Cc: gvb Subject: Provider claims 'it's normal that mysql crashes', is that true? Hello My provider 1&1-Puretec (www.puretec.de) hosting more than 1.000.000 domains runs about 14 Databaseserver with MySQL 3.22.32-log on Linux dual Penti-III 500Mhz machines. In the last 6 month the average uptime of the mysql-servers was around 8 hours. As I asked them why their mysql-server die so often, I got their standard problem email-answer that claims "mysql is scaling rather badly". After further asking I got a personal answer that says: "it's normal the mysql-servers die because of heavy load". "We can't help that the mysql task keeps crashing if to many users access it. That's totally normal for a mysql database" Is that true? regards Gunnar von Boehn
--------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
