| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "'pgsql-hackers(at)postgreSQL(dot)org'" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | AW: [HACKERS] RAW I/O device |
| Date: | 1999-12-07 10:42:35 |
| Message-ID: | 219F68D65015D011A8E000006F8590C603FDC1B0@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > Actually, Oracle has been moving *away* from this...more
> recent versions
> > of Oracle recommend using the Operating System file
> systems, since, in
This is untrue. They need the raw devices for their big DB's
(Parallel Server)
> > most cases, the Operating System does a better job, and its
> too difficult
> > to have Oracle itself optimize internal for all the
This is especially true for Oracle, since the don't have very
intelligent IO optimizations.
Good DB sided IO optimization can outperform any OS easily.
Especially once you reach the RAM limits of your system.
write cache, read ahead, indexed read ahead,
increased block size (up to 256k) .....
> different variants
> > that it supports....
There is not really that much difference.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB | 1999-12-07 11:06:08 | AW: [HACKERS] RAW I/O device |
| Previous Message | Zeugswetter Andreas SB | 1999-12-07 09:47:39 | AW: [HACKERS] RAW I/O device |