Re: Update or Insert -- Oracle 8.0.5 performance

Hi,

    Oracle buffers already buffers disk writes to the database. The redo
logs, which are sequential files, are written to immediately and the
table and index files are not updated until the blocks containing them
in the RAM cache are flushed.

    If you give Oracle enough RAM and tune your database properly you will have no performance problems -- at least none due to your
database I/O.

regards
Jerry Gitomer

ilyah_at_scour.net wrote in message <7pning$e3g$1_at_nnrp1.deja.com>...
>I am designing a web application in PHP that is connecting to
Oracle
>8.0.5. The application I am designing must be very quick -- I
cannot
>afford seconds of delay. Yet, I need to perform a few inserts
and a few
>updates.
>
>I have decided to buffer my inserts, doing them in bulk every
hour or
>so, offline. The web pages will be quick and some back-end
script will
>insert the data. Now, assuming my tables will have millions of
rows,
>should I do the same for updates?
>
>This boils down to the fact that I am not sure about select vs.
update
>vs. insert performance in Oracle. I have a few indexes on my
tables, so
>I am assuming that insert operations are going to be fairly
slow,
>selects are going to be fast enough to do from the pages in
realtime,
>and updates probably would be slower than the selects but a lot
faster
>than the updates. Does anyone know whether this assumption is
correct?
>Anyone have numeric or anecdotal information on the calls?
>
>-Ilya Haykinson
>
>
>Sent via Deja.com http://www.deja.com/
>Share what you know. Learn what you don't.
Received on Mon Aug 23 1999 - 08:29:00 CDT