Quote:
Originally Posted by The Geek
Why not just have a cron job that updates a row in the datastore whenever its called with the amount of posts made in a time frame?
|
I want to keep this as simple as humanly possible, adding crons and whatnot are too intensive in my eyes, I will figure this one out, no worries

Quote:
Originally Posted by The Geek
Doing an aggregate on the posts table (and users table) every page load will bring most large boards to their knees.
|
no, actually the implementation of this idea that was originally posted in the code mods section did that...killed MANY servers...
Quote:
Originally Posted by The Geek
I fact, if those queries were changed to 'today' instead of last visit... you could run a cron job nightly... save the results in the datastore... and eliminate most of your queries which in turn should bring your page generation down to a much more acceptable amount.
|
now, what use would the end user of the forum have in today's last posts? most everyone I've dealt with over the years only wants posts and threads since last visit. As far as the page generation time, .07 seconds of additional overhead is not a respectable number? In whose eyes?
Seriously though, I am working on getting this to talk with the datamanager as a cached thing, I don't want to add tables, or modify the db in anyway shape or form, but I will figure this out to kill off what little overhead there is right now. I have severa scenarios running on my test bed that have brought the page gen overhead down but I need to make sure that they are reliable methods first, my biggest concern at this point is the avatar...