[thesite] Caching

matt,
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> From: Warden, Matt
>> Yeah, I find it a lot more annoying than I thought I
> would. Take it out, I'd say.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
and see our execution times for the front page climb up over a second or
more? i personally get *very* tired of waiting for that front page any time
i try to visit the site. heck, it's 500ish milliseconds execution time now
with all the cached queries. to me, that's pushing it. i'd much rather
have it down around 100ms.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> Maybe we can set up something so that if we start
> getting a spike in traffic (like being slashdotted or
> something) we can run that script we used to have
> running that created a static version of the front page.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
that would be even worse than the caching. then, we'd have issues with the
sidebar not accurately reflecting whether you're logged in or not, urls
wouldn't have tokens for those users that don't accept cookies, comments and
ratings would not get updated at all except when the static version got
updated, etc.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> But, yeah, that query caching is rather annoying. I'm
> suprised there's no way to "uncache" the query when a
> change is made.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
there are ways. it simply requires combing through the code for each
process that runs that changes information that's displayed on the front
page and blasting the cached query out of memory so it runs from the
database and not from memory. the solution is definitely doable, but time
consuming.
.jeff
http://evolt.org/jeff at members.evolt.orghttp://members.evolt.org/jeff/