[Theforum] [---Dev] RE: [---tent] Article cleanup issue

[.jeff]

martin,

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> From: Martin Burns
>
> Right. So (excuse my SQL ignorance) is that returning
> pretty much everything about every signed off article
> in the db except:
> 1) certain categories (eg jobs)
> 2) the full article content
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

3) the id admin that signed off on the article (and the
   subsequent join or subquery necessary to get the user
   name that's associated with the id)
4) the date the admin changed the status last

if you'll notice on the homepage, these are all elements necessary for the display (at this time).

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> > so cfserver can cache it so subsequent hits in the
> > timespan allotted for the cached query don't have to
> > hit the database again.
>
> How many subsequent hits are there for articles not in
> the 1st page or 3?
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

no idea, but that's not the only people that benefit from the caching.

if you and i are both logged in today, we'd both benefit from the query caching because everything about the query is the same.  the same holds true for any other user visiting the homepage and logged in today.  so long as all the hits occur in the timespan allotted for the cached query, they all get the page back lightning quick because the display can be built from a query in memory.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> If those hits weren't cached, what would be the impact
> on:
> 1) the visitors to non-cached pages
> 2) the query times on the front page(s)?
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

all queries would take longer because every hit to the site would generate at least one or more database requests.

.jeff

http://evolt.org/
jeff at members.evolt.org
http://members.evolt.org/jeff/