Re: separate tablespaces for tables and indexes

what if you have 1000's  of people trying to access the table data at
the same time? Splitting the indexes and tables wont help because
there will always be contention at the disk level, not the tablespace
level.  The goal being make the number of io's being as small as
possible

The point is for a single session, splitting wont help you because
they are accessed serially - and that scales up as well


On Mon, 13 Dec 2004 13:41:52 -0600, Knight, Jon <jknight@xxxxxxxxxxxxxx> wrote:
> Sorry if I missed this already, but ...
> 
> Say session A has already read the index and is doing some datafile access,
> when along comes session B with an index range scan.  My understanding is
> that there's only one read/write head on the disk and contention results.
> Of course 10s or 100s of sessions would compound the issue.  Is this
> reasoning flawed?
> 
> Thanks,
> Jon Knight
--
http://www.freelists.org/webpage/oracle-l

Other related posts: