1. Manuals
  2. Brands
  3. Computer Equipment
  4. Server
  5. IBM
  6. Computer Equipment
  7. Server

IBM 000-8697 Eliminate User-Created Resource Bottlenecks

1 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 702
Download on canonical page 702 pages, 4.15 Mb
5-8 IBM Informix OnLine Database Server Administrator’s Guide

Apply Effective Criteria

Apply Effective Criteria

Looking at the efficiency information for blobspacebspc1 in Figure5-1, an
administrator might decide that a better blob-storage strategy would be to
doublethe blobpage size from 2048 bytes to 4096 bytes. (Recall that blobpage
sizeis always a multiple of the OnLine page size.) If the administrator made
this change, the measure of page fullness would remain the same but the
number of locks needed during a blob update or modification would be
reduced by half.
The efficiency information for blobspace blobPIC reveals no obvious
suggestionfor improvement. The two blobs in blobPIC differ greatly in size
andthere is no optimal storage strategy. In general, blobs of similar size can
be stored more efficiently than blobs of different sizes.
Eliminate User-Created Resource Bottlenecks
OnLine manages limited resources such as locks, latches, buffers, and log
space. Users can adversely affect OnLine performance by inadvertently
creating resource bottlenecks in an otherwise efficiently tuned OnLine
system. (You can monitor the shared-memory resources being held by user
processes by executing tbstat -u. Refer topage 3-86 or page page 7-99.)
Knowledgeableusers are able to avoid activities that can slow OnLine perfor-
mancefor everyone. As administrator, you should encourage users to follow
these four guidelines:
Donot leave a transaction open without committing or rolling back within
a reasonable period of time.
Ifa user leaves a transaction open, the resources held by the database
serverprocess are unavailable to other users. In addition, if the trans-
action is left open for an extended period, this user action can
become responsible for a long transaction error.
Do not stop a process using job control unless you are certain you can
terminate the job.
Astopped job does not release resources held by the database server
process.These resources might remain unavailable to other users. If
an application process is stopped while OnLine is engaged in data-
base activity on its behalf, serious concurrency delays can result.
MENU

Models

Contents