•
|
The L2 Cache is one component of the setting for Max MicroKernel Memory Usage. That setting specifies the maximum proportion of total physical memory that the database engine is allowed to consume, which includes L1 Cache, L2 Cache, and all miscellaneous memory usage by the database engine.
If the setting for Max MicroKernel Memory Usage is non-zero, the L2 Cache sizes itself to stay within the memory limit of the setting. The L2 Cache monitors memory consumption of the system and resizes itself as needed. The memory used by the L2 Cache may also be swapped out by the operating system.
|
||
See also Waits on Active Writer Lock counter.
|
||
See also Waits on Active Reader Lock counter.
|
||
The database engine writes changes to the data files during a system transaction. The frequency in which a system transaction occurs is determined by two server configuration parameters—Initiation Time Limit and Operation Bundle Limit—or triggered by a small amount of free space in the L1 Cache.
|
||
To determine the number of application transaction commits. See also End Transaction (20) in Btrieve API Guide.
|
1
|
Start Windows Performance Monitor. The steps vary depending on the operating system, but generally the utility can be started from Control Panel --> Administrative Tools. You may also try the command “perfmon” in the Run window (Start --> Run).
|
2
|
1
|
Right-click the desired counter, then click Properties.
|
3
|
Click OK.
|
4
|
5
|
Click OK.
|