|
Kevin,
Thanks for your input. I was trying to put certain
datafiles on contiguous disk space, tell me if I am wrong, I try to avoid the
situation where you want to create a 2G file, but the file system don't have a
2G contiguous space, so your flle is broken into multiple pieces, can that
happen??
KC
-----Original Message-----
From:
Kevin Lange <[EMAIL PROTECTED]>
To: Multiple
recipients of list ORACLE-L <[EMAIL PROTECTED]>
Date:
Wednesday, June 20, 2001 1:22 AM
Subject: RE: Disk
configuration
It
all depends on what kind of os/filesystem/and disks you have. I
know that under AIX, using SSA drives we could actually tell where on the
disk we wanted the filesystem to go. This way we could position
certain things in the faster location.
But personally, I would not go thru the trouble.
I
have never had a DB slowdown so far because of placement on the
drive. Admittadly, I have had probelms based on putting
conflicting tables/indexes on the same drive .... you want to keep things
that could be access simultaneously on different media. But
other than that .... no other conflicts.
Dear List,
Someone told me when a disk
receive a write request, it write to the nearest free space on disk
where the disk read/write head is currently positioning, is this
information correct?? If this is true, is this a bad thing for database
application?? That mean we can't really control where the file go, for
performance purpose we may want to put certain files on the outer tracks
of a disk, if the write location is depending on where the read/write
head is, how can we avoid that, can we create subdisks from the outer
track of a disk and create a logical volume from it??
KC
|
