My products home page has 4 sections of data that should ideally be updated at every page load, how can I do this without killing my database server?
Ask HN: Now can I cut down mySQL queries on dynamic pages?
1–4 of 4 posts
Re: Ask HN: Now can I cut down mySQL queries on dynamic pages?
#2If it has to be updated on every page load I don't think there's anything you can do...I may be wrong I'm sure someone on HN will have some performance tricks. You can generate your headers and footers and store them in a file instead of touching a database every time. If you're killing your database server you're probably returning too many records or your queries suck. I wouldn't know without seeing them.
Re: Ask HN: Now can I cut down mySQL queries on dynamic pages?
#3The only way to improve it is cache it for maybe x minutes, and then update cache. Maybe you should provide the reason why it can't be cached for say maybe 5 minutes. If its a problem where they are reloading, the homepage to see results then you could do incremental updates of each section using comet technique.
Re: Ask HN: Now can I cut down mySQL queries on dynamic pages?
#4The only way to improve it is cache it for maybe x minutes, and then update cache. Maybe you should provide the reason why it can't be cached for say maybe 5 minutes. If its a problem where they are reloading, the homepage to see results then you could do incremental updates of each section using comet technique.
This is probably a more practical method.