solidDB® includes means for monitoring and collecting data on the type and number of SMA connections as well as the SMA memory segment sizes.
▪Use ADMIN COMMAND 'userlist' to print a list of the type of user connections (network client or SMA client).
▪Use ADMIN COMMAND 'report' to print a list of the connections by the type.
▪Check the solmsg.out file login entries for the type of the connections made.
▪Use the performance counter SMA connection count to collect data on the number of SMA connections.
▪Use the performance counter SMA shared memory used to collect data on the SMA memory segment size.
For details on using the ADMIN COMMANDs, the solmsg.out, and the performance counters, see solidDB® Administrator Guide.
Measuring processor utilization in SMA-based databases
The SMA server process (solidsma) cannot be used to measure the processor utilization of the database used by SMA applications. With SMA, most of the solidDB® server code executes in the application’s address space. On the other hand, the processor utilization reported for an SMA application reflects both the load inflicted by the application code itself and the solidDB® code invoked to process the application’s request.
If the applications are not processor-intensive, the best approximation of the processor utilization of the total database system is the sum of the processor utilization values of all the SMA applications and the SMA server process.
The SMA server process consumes very little of the processor capacity in its own address space. The server process consists of only housekeeping and asynchronous tasks like checkpointing, backup, and so on.