From: Simon J Mudd Date: March 17 1999 1:12pm Subject: Re: beeing informed of changes in rows in a table (real-time prices) List-Archive: http://lists.mysql.com/mysql/416 Message-Id: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 17 Mar 1999, Michael Widenius wrote: > Note that in most cases with SQL the performance is depending on how > many new disk blocks you are accessing. > > If you have an timestamp on each row and only do selects based on > recent timestamps, MySQL will only access the same disk buffers over > and over again. Most OS cache this very good and you have to do real > many queries to get any significant load. Ok, this may well help me initially. > In MySQL 3.23 we will extend > > SHOW TABLES > > to include a lot of information about each table ! [snip] > - Last changed ! > I assume the above will help you with your problem! Yes, using this will reduce the potential load on the server, and enable me to do the real SELECTs once I know there have been changes. In the meantime I think using a timestamp in the table, and keeping an eye on the load will give me an idea of how frequently I can request the data. Thanks for your comments, Simon Simon Mudd ******** All Trading Brokers Europe ********* Madrid, Spain Switchboard: +34-91-592 8188 Fax: +34-91-592 8170 Direct: 91-592 8250 Work email: simon.mudd@stripped --- Home email: sjmudd@stripped