[thelist] pretty databases vs. fast databases

[Emma Jane Hogbin]

On Sun, Mar 09, 2003 at 05:51:39PM -0600, Erik Mattheis wrote:
> Even if the initial 100 users increases to 10,000 and each of those
> 10,000 views 5 pages in an 8 hour burst, that's still less than 2
> queries per second. So unless the DB you're using is something worse
> for the web than Access '97, the end user is going to see no
> difference

Cool. This is good to know. :)

> On the other hand, if handling a large load as best as possible is a
> goal of the project, a non-normalized design might be the better way to
> go ... unless your app is going to have to update the non-normalized
> stuff quite a bit more than I'd assume given the names of the columns
> in your queries.

I'd already have a db query open to update the IDs so it wouldn't be that
much extra work to update some other columns in the same table while I was
at it...it's more the speed of the selects that I was worried about.

> Not that you asked the question, but a way to completely eliminate the
> potential problem would be to write static files from the queries
> instead of querying the DB with each request.

Yup. that's the publishing system that I eluded to at the bottom
of the post. I'd love to have a system that output XML
files + transformations each time a "save" was done. Then visitors would
pick up the correctly transformed file. (The "raw" XML files could be used
for content syndication/distributed archives/etc.)

emma

--
Emma Jane Hogbin
[[ 416 417 2868 ][ www.xtrinsic.com ]]