Kbase P49008: How to take advantage of an Enterprise database
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
GOAL:
How to take advantage of an Enterprise database
GOAL:
How to implement advantages of an Enterprise license
FIX:
See below a list of startup options to use and process to start for taking advantage of an Enterprise license (versus a Workgroup license).
You will find here guidelines; for the best tuning on your system, you may want to have a Progress consultant on site.
."spin" startup parameter
By using spin locks instead of the usual system of semaphores and queues, the waiting time on lock is reduced.
Use "-spin 1" if you are on a monoprocessor machine, use "-spin X" with X=2000 multiplied by the number of processors on your machine otherwise.
. "semsets" startup parameter
With "-semsets X", the database will use X different semaphore sets.
The default is having just on semaphore set. We do recommend to have an additional semaphore set per 1000 users (for example "-semsets 3" for 1500 users).
. Before Image Write (BIW) process
You may start one (and only one) BIW process per database, with the command
probiw <dbname>
That process will flush to disk the BI buffers. Make sure you have no "BI Buffers wait" which would make the BIW process less beneficial.
. After Image Write (AIW) process, if you do run After-Imaging
You may start one (and only one) AIW process per database, with the command
proaiw <dbname>
That process will flush to disk the AI buffers.
. Asynchronous Page Write (APW) processes
You may start as many as you want APW processes for a database, with the command
proapw <dbname>
These processes will flush to disk the modified database blocks from the buffer pool.
Additionally, you might want to take advantage of the command "proquiet" which allows to stall the database (the time you split mirror for example) and of the large file support with the command "proutil <dbname> -C EnableLargeFiles".
Also available with Enterprise license only are the empty databases with a block size different from the default one (1K on UNIX, 4K on Win32 platforms).
On UNIX it is recommended, for better performance, to have 8K block database (empty8.db). Unfortunately you will need to use the dump/load strategy when having decided to change the DB block size; the first step will be creating a new database with the command
prostrct create <dbname> -blocksize 8192