OpenEdge Management and OpenEdge Explorer: Configuration

Configuring OpenEdge Databases
2–8
Table 2–2: General database configuration properties (2 of 2)
Property Description
Maximum private
database buffers per user
Controls the number of private buffers a connection can
request through the Private Read-only Buffers (-Bp)
parameter.
Direct I/O Enables the Direct I/O property, which opens all files in
unbuffered mode. Direct I/O enables the database to
use an I/O technique that bypasses the operating system
buffer pool and transfers data directly from a buffer to
disk.
This technique has some advantages over buffered
reads and writes, such as avoiding the overhead of
maintaining the operating system buffer pool, and
eliminating competition for operating system buffers
between the database and other programs. The
operating system buffer-pool algorithms are designed
for efficient sequential file access; the OpenEdge
buffer-pool algorithms are more efficient for access to
an OpenEdge RDBMS.
The Direct I/O check box is cleared by default.
Other arguments Any other arguments for which there is no defined
property available.
Table 2–3: Background writers database configuration properties
(1 of 3)
Property Description
Watchdog process Start the Watchdog process automatically
when the database starts.
The check box is selected by default.
Asynchronous page writers The number of Asynchronous Page Writer
(APW) processes to start.
A database can have between zero and nine
APWs running simultaneously. The optimal
number is dependent on your application and
environment.
To start, use one page writer for each disk
where the database resides. If this is
insufficient, add more.
For an application that performs many
updates, start one APW for each disk
containing your database, and add one
additional APW. Applications that perform
fewer changes to a database require fewer
APWs. If an application performs no updates,
no page writers are required.
The default value is 1.