Tuning Question
Date: Thu, 13 Apr 2000 16:01:48 GMT
Message-ID: <8d4r11$lqi$1_at_nnrp1.deja.com>
[Quoted] We are developing a large-scale computer simulation which uses an Oracle database for storage and retrieval of data. In particular, we have a construct called an "Instrument" which, during the course of the simulation run, will collect sample data and insert it into an Oracle table. Due to the nature of the data, it must be stored in binary form. So, our table is of the form:
DATA_KEY (VARCHAR2) | DATA_OBJECT (LONG RAW) Insertion occurs one row at a time, one transaction at a time. That is, a "commit" occurs after each individual insertion.
However, we have one small problem: A simulation run without instruments takes an hour or two. A run with all instruments turned on can take *DAYS* to complete, most of the time spent in Oracle accesses.
I'm about to attempt to tune our Oracle accesses, using "Oracle Server Tuning" as a guide. But before I do, a question for the group: Do the symptoms I have been describing sound familiar? Has anyone encountered anything like this before? Does an obvious solution to this problem present itself? If not, what areas would you look at first?
And a related question:
Part of the fix may involve re-writing our application's C-level call
interface -- where can I find a good guide to this architecture, and to
interacting with Oracle at this level? The manuals shipped with the
server are useful, but somewhat non-intuitive.
Many thanks for any assistance you can offer.
Very Respectfully,
Brian P.
Sent via Deja.com http://www.deja.com/
Before you buy.
Received on Thu Apr 13 2000 - 18:01:48 CEST