Re: Moving to a faster machine does not improve performance
Posted by:
James Day
Date: January 14, 2005 03:58PM
Take a look at SHOW INNODB STATUS while hte system is under normal load. What are connections waiting for? Are the queries using the indexes you expect?
If you find that there are many daemons after the same records or index blocks you might consider trying several queues, perhaps for different types of work, and having the slaves poll each in turn.
If there is a single queue, you might consider using a queue daemon which responds to requests from slaves and updates the database itself. Atlernatively, there are some non-database functions in MySQL which may be of use - IS_FREE_LOCK, GET_LOCK and friends. If your applications are nicely cooperating you can use those to dodge the database storage engine without having to switch to a daemon. If you have simple task identifiers it may be relatively easy to use those to try to grab a lock on a task before switching to the storage engine for the final part of the status change. May or may not be less work for you.
Subject
Views
Written By
Posted
3029
January 13, 2005 01:28PM
1940
January 13, 2005 03:27PM
1938
January 13, 2005 04:13PM
1961
January 14, 2005 10:59AM
Re: Moving to a faster machine does not improve performance
1926
January 14, 2005 03:58PM
1921
January 15, 2005 08:21AM
1982
January 19, 2005 12:30AM
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.