Tuning MySQL
I have a quad processor server, with 4 gigs of memory. It is only running MySQL right now and seems really slow. Can someone give me a few suggestions on optimizing My.cnf file for this system. We are running mysql-standard-4.0.23-pc-linux-i68, on it. Here is the my.cnf file # The MySQL server [mysqld] port= 3306 socket = /tmp/mysql.sock skip-locking key_buffer = 384M max_allowed_packet = 2M table_cache = 512 sort_buffer_size = 2M read_buffer_size = 2M myisam_sort_buffer_size = 64M thread_cache = 8 query_cache_size = 32M # Try number of CPU's*2 for thread_concurrency thread_concurrency = 8 user=mysql basedir=/usr/local/mysql datadir=/usr2/mysql/data max_connections=400 max_connect_errors=300 interactive_timeout=2400 wait_timeout=60 back_log=100 #skip-networking server-id = 2 [isamchk] key_buffer = 256M sort_buffer_size = 256M read_buffer = 2M write_buffer = 2M [myisamchk] key_buffer = 256M sort_buffer_size = 256M read_buffer = 2M write_buffer = 2M -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: on big mysql .MYD files and linux's 2GB file size limit
Depends on what file system you are running that is a ext2 limit if you move to ext3 or reiser you should be fine. But then a default config on MySQL will run into a 4.29 Gig limit, which you can change. Eric Gunnett System Administrator Zoovy, Inc. [EMAIL PROTECTED] >>> "Shannon R." <[EMAIL PROTECTED]> 08/02/04 06:58PM >>> Is the 2GB filesize limit in linux still there? Specially in Gentoo and Debian linux? If so, how can this be addressed when your mysql's .MYD files reach 2GB? Is there any way MySQL can split really big .MYD files? Regards, Shannon __ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail -- 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]
Re: Bin-logs
You can do a reset master, and it will start the log over at 001 and remove the old log files that are there. Eric Gunnett System Administrator Zoovy, Inc. [EMAIL PROTECTED] >>> Jeff Smelser <[EMAIL PROTECTED]> 06/15/04 11:26AM >>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am trying to prune some bin-logs and noticed: mysql> show master logs; ++ | Log_name | ++ | db-bin.001 | | db-bin.002 | | db-bin.003 | | db-bin.004 | | db-bin.005 | | db-bin.006 | | db-bin.007 | | db-bin.008 | | db-bin.009 | | db-bin.010 | | db-bin.011 | | db-bin.012 | | db-bin.013 | | db-bin.014 | | db-bin.015 | | db-bin.016 | | db-bin.017 | | db-bin.018 | | db-bin.001 | | db-bin.002 | | db-bin.003 | | db-bin.004 | ++ 22 rows in set (0.01 sec) I recently redid the replication and it restarted at 001.. Well the 001-018 doesn't exist on my server. So I get: mysql> PURGE MASTER LOGS TO 'mysql-bin.004'; ERROR: Target log not found in binlog index How do I get rid of the 000-018 files that don't belong there? Thanks, Jeff - -- If you're going to walk on thin ice, you may as well dance. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAzz9tld4MRA3gEwYRAjquAKDYbTb1XHZUhJ/V8KZssZUS3AlrBACgrLUH mokZhloHPfIMBm9Txu2QmLk= =CCMg -END PGP SIGNATURE- -- 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]
Re: MySQL on Linux
I have had this happen on 2 boxes one running Redhat 7.2 and the other running Redhat 8. I can tell MySQL does not like not being able to write to the file anymore. We were using MySQL 3.23 on one box and 4 on the other box. The table crashed. Causing a lot of corruption. In one instance it actually took the table and zeroed it out leaving me with no data, and having to recover the 2 gig table, then watching it happen again. Eric Gunnett System Administrator Zoovy, Inc. [EMAIL PROTECTED] >>> Alan Williamson <[EMAIL PROTECTED]> 04/06/04 02:47PM >>> dan wrote: > the most popular would have been Red Hat, which doesn't have this limit > you speak of, even plain vanilla install (no twiddling needed). Not to spoil a perfectly good pontification ... but i have to say that we have a Redhat8 distribution running on a Dell PowerEdge Server and when Apache gets to the 2GB size on its access file, it does indeed stop. This is not old hardware (12months old). So don't be spouting any sweeping statements. If your distribution doesn't have that limitation, then fantastic, good for you. But for others it is indeed a real limitation. The original question was indeed a geniue one, and while the poster accidently typed in the wrong size, i wouldn't be so quick to jump all over him. So the question still remains. What would happen in MySQL when that file isn't allowed to grow any further? -- 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]
Tru64_Unix
First time poster so let me know if there is anymore information you need. We have been have a problem with our database ever since we upgraded it from 3.23 to 4.0.15a. IT is being run on a Tru64 Unix box with several gigs of memory. Every 2 weeks roughly the database seems to slow down to almost a crawl, we reindex all of the tables and that help but what really solves the problem is restarting the database. The memory usage goes down to nothing after the restart. Grows a little bit as the table cache is populated, and then will stay that way for several days. Then the memory usage will slowing begin to climb, until after 2 weeks the database is barely able to process a simple select statement? Can you guys give me some ideas on what it possibly could be, right now I am thinking it is a memory leak. But would love to get some recommendations on what steps I can take to isolate and eliminate this problem? Eric Gunnett System Administrator Zoovy, Inc. [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql_install_db problem
I am having the same problem, and can't seem to find a work around. If you go to version 29a I believe it works fine. -Eric >>> Titus Purdin <[EMAIL PROTECTED]> 03/08/01 11:25AM >>> I am installing mysql-3.23.33-dec-osf5.1-alphaev6 on a DEC Alphastation running True64 Unix version 5.0A. Logged in as root, when I run scripts/mysql_install_db as part of the installation, it runs as far as % scripts/mysql_install_db Preparing db table Preparing host table Preparing user table Preparing func table Preparing tables_priv table Preparing columns_priv table Installing all prepared tables and appears to hang. I let it run for several hours and it continued to use cycles, but was making no apparent progress. Insights appreciated. titus sends - 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 - 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
