|
Pmon
|
Description
|
|---|---|
|
File open
|
File open calls per second.
High numbers can indicate excessive disk I/O.
Internally in the solidDB server, a wrapper function is around the fopen() system call. Each time a file is opened, this counter is incremented. Opening a file is an expensive operation in itself but also indicates that a read or a write to a file is required. This counter should be low when using only in-memory tables.
Note Other database operations such as checkpointing, logging, diagnostics (tracing and log messages) require file opens so this counter might not be zero.
|
|
File read
File write |
File read/write calls per second.
High numbers can indicate excessive disk reads or writes.
Internally in the solidDB server, wrapper functions are around the read() and write() system calls. Each time these wrapper functions are called to read or write from a file, the respective pmon counter is incremented. Therefore if you see large numbers in these counters and you expect all of your tables to be in memory, you might have a problem that should be investigated.
Note Other database operations, such as checkpointing, logging, and diagnostics (tracing and message logs) require file reads and writes. Make consideration for such events when analyzing these counters.
|
|
File append
|
File append calls/sec
|
|
File flush
|
File flush calls/sec
|
|
File lock
|
File lock calls/sec
|
|
File read bytes
|
File read bytes/sec
|
|
File write bytes
|
File write bytes/sec
|