Re: mysql q

On 11/17/2013 3:39 PM, Erez D wrote: On Sun, Nov 17, 2013 at 10:36 AM, ik wrote: Hi, I think you tackle it wrong. If there is no nee

Re: mysql q

On Sun, Nov 17, 2013 at 3:39 PM, Erez D wrote: > > > > On Sun, Nov 17, 2013 at 10:36 AM, ik wrote: > >> Hi, I think you tackle it wrong. >> >> If there is no need for accessing the database all the time, why not >> cache the result in tools such as Memcached or Redis ? >> > then i will still nee

Re: mysql q

On Sun, Nov 17, 2013 at 10:36 AM, ik wrote: > Hi, I think you tackle it wrong. > > If there is no need for accessing the database all the time, why not cache > the result in tools such as Memcached or Redis ? > then i will still need to poll Memcached or Redis. this may speedup things, but it is

Re: mysql q

In similar line to some of the other suggestions: 1. A cache sounds like a must here. 2. Make the process which updates the database to also clear the cache to trigger a refresh. On 17 November 2013 19:18, Erez D wrote: > hello > > i have a web page that refreshes all the time to display thing

Re: mysql q

I don't know about triggers, but you could have a caching mechanism server side, which queries for last update to determine whether a new page needs to be rendered and serves the cached page. You could also make sure that the auto refreshes cause only the relevant queries and not all the queries i

Re: mysql q

Hi, I think you tackle it wrong. If there is no need for accessing the database all the time, why not cache the result in tools such as Memcached or Redis ? If they are different clients (as in agents), then there are other tools at your disposal, such as Varnish, that create cached version for th

mysql q

hello i have a web page that refreshes all the time to display things from a mysql database which is updated from time to time. however. this meens a lot of un-needed acesses to the database. and this refresshing page may be openede by many browsers. causing a huge load on the database. i know my