MySQL Forums
Forum List  »  Performance

Re: Monitoring large resultsets
Posted by: Jerome Benezech
Date: July 12, 2012 05:35AM

- Cache size. I've read that 2GB could cause problem on 32 bit system. But I'm afraid that if I set it lower, even more CPU will be used.
Linux Server usually has 3-4GB free RAM.

- tmp_table_size. Again, there is available memory on the server. Also when using top, I never see mysql taking more than 2.1GB which is basically the cache size. Not sure what to make out of this ?

- Connections/back_log. This is interresting but not sure what to make out of it. Connections are waiting because previous ones took too long and keep the server busy. If I increase this, they'll just be more waiting.

- tmp disk tables. Again that comes down to coding. As I understand, they are used for some joins and ordering.

- data sent / nbr selects. That's a lot indeed considering there are max 15 php clients at a time. 48 Kb / client / second.

All in all, do you think this only comes down to query optimization ? My MySQL takes 8s to serve a query it take 0.02s to serve when not busy ? Is it waiting for I/O (but low iowait in top), CPU time (but 8 cpus), RAM (but always 3GB available) ?

Options: ReplyQuote


Subject
Views
Written By
Posted
2046
July 10, 2012 10:26PM
1114
July 11, 2012 02:01AM
896
July 12, 2012 02:19AM
946
July 12, 2012 03:37AM
940
July 12, 2012 04:13AM
Re: Monitoring large resultsets
920
July 12, 2012 05:35AM
982
July 12, 2012 05:49AM
1113
July 12, 2012 07:02AM
933
July 13, 2012 07:50PM
918
July 14, 2012 02:43AM
901
July 12, 2012 08:13AM
897
July 12, 2012 08:55AM
981
July 12, 2012 12:12PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.