Hi, Signal 11 can also indicate hardawre problems on BSD. Also FreeBSD might get you more answers quickly as there are more of us running FreeBSD with MYSQL for some reason. We runn FreBSD w MySQL/Linux threads on 4.9 and 5.2 and both work just fine.
Ken ----- Original Message ----- From: "RV Tec" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 18, 2004 9:28 AM Subject: MySQL limits. > Folks, > > I have a couple of questions that I could not find the answer > at the MySQL docs or list archives. Hope you guys can help me. > > We have a database with approximately 135 tables (MyISAM). > Most of them are small, but we have 5 tables, with 8.000.000 > records. And that number is to increase at least 1.000.000 > records per month (until the end of the year, the growing rate > might surpass 2.000.000 records/month). So, today our database > size is 6GB. > > The server handles about 35-40 concurrent connections. We have > a lot of table locks, but that does not seem to be a problem. > Most of the time it works really well. > > >From time to time (2 weeks uptime or so), we have to face a > Signal 11 crash (which is pretty scary, since we have to run a > myisamchk that takes us offline for at least 1 hour). We > believe this signal 11 is related to the MySQL server load > (since we have changed OS's and hardware -- RAM mostly). > > Our server is one P4 3GHz, 2GB RAM (400mhz), SCSI Ultra160 > 36GB disks (database only) running on OpenBSD 3.5. We are > aware that OpenBSD might not be the best OS for this > application... at first, it was chosen by it's security. Now > we are looking (if that helps) to a OS with LinuxThreads > (FreeBSD perharps?). > > The fact is that we are running MySQL on a dedicated server, > that keeps the load between 0.5 and 1.5. CPU definitively > is not a problem. The memory could be a problem... our > key_buffer is set to 384M, according to the recommendations at > my-huge.cnf. So, it seems we have a lot of free memory. We > have already tried to increase key_buffer (along with the > other settings), but it does not seem to hurt or to improve > our performance (although, the memory use increases). > > To track down this signal 11, we have just compiled MySQL with > debug and returned to the original my-huge.cnf > recommendations. Now it seems we are running on a overclocked > 486 66mhz. > > Is there any way to prevent this signal 11 to happen or is it > a message that we have exceeded MySQL capability? > > Is MySQL able to handle such load with no problems/turbulences > at all? If so, what would be the best hardware/OS > configuration? > > What is the largest DB known to MySQL community? > > If it's needed, I can provide DMESG, MySQL error log, compile > options and some database statistics. > > Thanks a lot for your help! > > Best regards, > RV Tec > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
