Physical database design options include
separating a single table into multiple tables, and the reverse??”combining multiple tables into
one. The emphasis should be on providing the users the most direct path possible to the data they
want in the format they want.
Distribution of CPU Requirements
When effectively designed and given adequate hardware, an Oracle database application will
process I/O requests without excessive waits, will use memory areas without swapping and
paging memory to disk, and will use the CPU without generating high load averages. Data that is
read into memory by one process will be stored in memory and reused by many processes before
it is aged out of memory. SQL commands are reused via the shared SQL area, further reducing the
burden on the system.
If the I/O burdens of the system are reduced, the CPU burden may increase. You have several
options for managing the CPU resources:
The CPU load should be scheduled. You should time long-running batch queries or
update programs to run at off-peak hours. Rather than run them at lower operating
system priority while online users are performing transactions, run them at normal
operating system priority at an appropriate time. Maintaining their normal priority level
while scheduling the jobs appropriately will minimize potential locking, undo, and CPU
conflicts.
Take advantage of the opportunity to physically shift CPU requirements from one server
to another.
Pages:
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408