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
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
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 erez0...@gmail.com wrote:
hello
i have a web page that refreshes all the time
On Sun, Nov 17, 2013 at 10:36 AM, ik ido...@gmail.com 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
On Sun, Nov 17, 2013 at 3:39 PM, Erez D erez0...@gmail.com wrote:
On Sun, Nov 17, 2013 at 10:36 AM, ik ido...@gmail.com 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 ?
On 11/17/2013 3:39 PM, Erez D wrote:
On Sun, Nov 17, 2013 at 10:36 AM, ik ido...@gmail.com wrote:
Hi, I think you tackle it wrong.
If there is no need