From: "Fernando Dammous" <ferdam@internetcom.com.br>
To: freddy@sk.oracle.com
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Linux LVM msede <linux-lvm@msede.com>
Subject: Re: [linux-lvm] LVM, raw-io, devfs
Date: Sun, 3 Oct 1999 14:23:38 -0300 [thread overview]
Message-ID: <002301bf0dc4$094485e0$030116ac@fd1> (raw)
In-Reply-To: 19991003121415.A30243@redneck.sk.oracle.com
Hi (again!),
From: Adrien Farkas <freddy@redneck.sk.oracle.com>
> Forget it, Linux port of Oracle DB doesn't support raw-io.
I admit that I'm not a deep expert of Oracle, mainly regarding interaction
with the I/O devices and with the operating system.
However, I have been finding in the documentation of Oracle for Linux,
several references of utilization of RAW-DEVICES (among others).
I'm not, here, wanting to create controversy, because it is dealt with a
matter extra-LVM and being you a member of Oracle (I saw for your e-mail
address freddy@sk.oracle.com), you must have knowledge of this subject. Then
I ask:
What does mean the references about RAW-DEVICES in documentation?
To illustrate, I separated some from :
Oracle8 Administrator's Reference for LINUX
Release 8.0.5
A66585-01
<SNIP>
- Tuning of I/O Loads across all Drives
I/O loads are tuned across all drives, including drives storing Oracle data
in raw devices
<SNIP>
- Raw Device Sizes
Choose a small set of standard sizes for all raw devices that may be used to
store Oracle database files.
In general, standardizing on a single size is recommended. If a single size
is used, raw files can be moved from one partition to another safely. The
size should be small enough so that a fairly large number can be created,
but large enough to be convenient.
For example, a 2 GB drive could be divided into 10 partitions of 200 MB
each-a good balance between size and number. Any tablespace using raw
devices should stripe them across several drives. If possible, the striping
should be done with a Logical Volume Manager."
<SNIP>
- Tuning the LINUX Buffer Cache Size
To take full advantage of raw devices, adjust the size of the Oracle8 buffer
cache and, if memory is limited, the LINUX buffer cache.
The LINUX buffer cache is provided by the operating system. It holds blocks
of data in memory while they are being transferred from memory to disk, or
vice versa.
The Oracle8 buffer cache is the area in memory that stores the Oracle
database buffers. Since Oracle8 can use raw devices, it does not need to use
the LINUX buffer cache.
When moving to raw devices, increase the size of the Oracle8 buffer cache.
If the amount of memory on the system is limited, make a corresponding
decrease in the LINUX buffer cache size.
The LINUX command vmstat may help you determine which buffer caches should
be increased or decreased.
<SNIP>
------------------------
Cheers and sorry for the long mail!
Fernando
next prev parent reply other threads:[~1999-10-03 17:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-01 2:48 [linux-lvm] LVM, raw-io, devfs Fernando Dammous
1999-10-01 12:40 ` Adrien Farkas
1999-10-01 16:38 ` Stephen C. Tweedie
1999-10-01 18:39 ` Drew Smith
1999-10-01 19:15 ` Luca Berra
1999-10-02 15:01 ` Stephen C. Tweedie
1999-10-02 15:53 ` Eric Smith
1999-10-03 7:43 ` Harald Milz
1999-10-02 17:08 ` Fernando Dammous
1999-10-03 5:56 ` pamvdam
1999-10-04 10:43 ` Stephen C. Tweedie
1999-10-04 11:03 ` pamvdam
1999-10-03 10:14 ` Adrien Farkas
1999-10-03 17:23 ` Fernando Dammous [this message]
1999-10-04 9:28 ` Adrien Farkas
1999-10-04 10:44 ` Stephen C. Tweedie
-- strict thread matches above, loose matches on Subject: below --
1999-10-03 13:06 Daniel Whicker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002301bf0dc4$094485e0$030116ac@fd1' \
--to=ferdam@internetcom.com.br \
--cc=freddy@sk.oracle.com \
--cc=linux-lvm@msede.com \
--cc=sct@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.