MySQL performance opt for a 5000 connection web site?
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
MySQL performance opt for a 5000 connection web site?
Hi all,
I am new on MySQL, and I had my own server host at home with CentOS 6.2 install LAMP by default setting, and it is hosting my Photo Blog.
It using WordPress and NextGen Gallery, special on NextGen Gallery have a big table with hold all my photo id one by one. It will make the MySQL slowly down? or on default cache size too low on the CentOS 6.2 install?
This MySQL server has been running for 8 days, 11 hours, 58 minutes and 19 seconds. It started up on Jan 22, 2012 at 10:52 PM.
Query statistics: Since its startup, 1,750,319 queries have been sent to the server.Documentation
Innodb_buffer_pool_readsDocumentation 97 The number of logical reads that InnoDB could not satisfy from buffer pool and had to do a single-page read.
Innodb_row_lock_waitsDocumentation 1 The number of times a row lock had to be waited for.
Handler_read_rndDocumentation 2.5 M The number of requests to read a row based on a fixed position. This is high if you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan whole tables or you have joins that don't use keys properly.
Handler_read_rnd_nextDocumentation 47.3 M The number of requests to read the next row in the data file. This is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have.
Created_tmp_disk_tablesDocumentation 21.2 k The number of temporary tables on disk created automatically by the server while executing statements. If Created_tmp_disk_tables is big, you may want to increase the tmp_table_size value to cause temporary tables to be memory-based instead of disk-based.
Opened_tablesDocumentation 347 The number of tables that have been opened. If opened tables is big, your table cache value is probably too small.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.