Re: Target number of database reads per user
From: Louis Davidson (dr_dontspamme_sql_at_hotmail.com)
Date: 11/24/04
- Next message: Louis Davidson: "Re: Table Variable vs Temporary Table"
- Previous message: Tibor Karaszi: "Re: Fit table on one page if possible?"
- In reply to: Andrew J. Kelly: "Re: Target number of database reads per user"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 24 Nov 2004 09:36:17 -0600
Yeah, just to echo what Andy is saying, if you want to have the question
answered of how many reads you should have (where did you get the 300
number?) you have to look at your design. The part of the original post
that scares me is:
>> Currently we are doign around 1800 database reads, with the majority
>> of those (around 1200) only happening if/when the user purchases
>> items).
On purchase, you should have a very very small number of reads. Searching,
logging, and trying to match up a users tastes with a page to display, or
even simple searches I might see this many reads, or even more. But the
types of operations you are talking about with a creation operation such as
a purchase of items should be very straightforward, key access oriented
operations. If you can post code/database design we could all take a look.
-- ---------------------------------------------------------------------------- Louis Davidson - drsql@hotmail.com SQL Server MVP Compass Technology Management - www.compass.net Pro SQL Server 2000 Database Design - http://www.apress.com/book/bookDisplay.html?bID=266 Note: Please reply to the newsgroups only unless you are interested in consulting services. All other replies may be ignored :) "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message news:%23nthVgj0EHA.424@TK2MSFTNGP14.phx.gbl... > When it comes to performance less reads is always better. But how many is > totally dependant on what you need to do and how it was designed. There > is no straight forward answer in that regard. The goal is get each db > call optimized such that it has as few reads as possible to get the > required work done. > > -- > Andrew J. Kelly SQL MVP > > > "Andy" <andrew@thevalley.f9.co.uk> wrote in message > news:5d7cc30e.0411240702.7f36de1@posting.google.com... >> We are currently developing a high traffic digital music e-commerce >> site using ASP.NET and SQL Server. Does anybody have any suggestions >> for what a good number of database reads per user (from inital site >> entry to checkout and delivery of media files). Ideally we need to be >> able to handle in the region of 100,000 sales per day, and up to 10 >> times that in site visitors. >> >> Currently we are doign around 1800 database reads, with the majority >> of those (around 1200) only happening if/when the user purchases >> items). >> >> Is that too high? We were advisted that we should be aiming for 300 >> reads per complete transaction, but that is impossible with the >> current system design, and from my point of view, impossible with the >> currentl SQL Server query optimiser (we have one stored procedure >> doing 380 reads despite it being a simple join between indexed >> fields). >> >> Many Thanks >> Andy Oakey > >
- Next message: Louis Davidson: "Re: Table Variable vs Temporary Table"
- Previous message: Tibor Karaszi: "Re: Fit table on one page if possible?"
- In reply to: Andrew J. Kelly: "Re: Target number of database reads per user"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
