Solaris Performance Counters for the Operating System

Sun Microsystems created the Unix-based operating system Solaris, which is now owned by Oracle. It is intended for use with the x86, IA-64, and SPARC architectures. Many major enterprise settings and cloud computing solutions employ Solaris as their server operating system. In addition to virtualization, clustering, high availability, scalability, and security, it offers a variety of other characteristics. In addition, Solaris is renowned for its dependability and toughness. With support for languages like Python, C, C++, and Java, Solaris is frequently used as a development platform.

Solaris Operating System Performance Counters

System

  1. CPU User: The amount of time spent executing non-kernel programs (including enjoyable time). time spent on the CPU as a percentage.
  2. CPU System: The amount of time used to execute kernel code. time spent on the CPU as a percentage.
  3. CPU Inactivity: CPU inactivity. % breakdown of CPU time used.
  4. Interruptions Count: The number of interruptions every second, including the clock, is known as the interruptions count.
  5. Context Switch Rate: The frequency of context transitions.
  6. Context Switch Count: The number of context switches made by each CPU each second.
  7. Processes Runnable: The number of processes that are awaiting execution.
  8. Processes Runnable per CPU: The quantity of processes each CPU has available for execution.
  9. Processes Sleeping: The number of processes resting soundly.
  10. Processes Changed: The number of processes changed but still able to run. Although this field is calculated, Linux never uses desperate swaps.

Memory

  1. Available Swap Space: The amount of swap space that is at present (in Kbytes).
  2. Free List Size: Size of the free list, expressed in Kbytes.
  3. Page Reclaims Per Second: Provide details regarding page errors by providing page reclaims per second.
  4. Minor flaws Per Second: Report details about minor flaws on the page.
  5. Paged In Per Second:  Kilobytes are paged in at a rate of one every second.
  6. Paged Out Per Second: Kilobytes are paged out once every two seconds.
  7. Freed Per Second:  Kilobytes per second are released for free.
  8. Short-term Memory Shortfall: Short-term memory shortfall anticipated in Kbytes per second.
  9. Pages Scanned by Clock Algorithm: Pages are scanned once every second by the clock algorithm.

Disk (per device)

  1. Disc Read: The volume of read requests sent to the device in a single second.
  2. Disc Write The number of write requests sent to the device per second.
  3. Disc Read (KB): The amount of data read per second in Kilobytes.
  4. Disk Write (KB): Β Kilobytes written per second for disc writing (KB).
  5. Transaction waiting for service: pending transaction requiring service Average number of transactions in the queue for service.
  6. Average number of transactions:Β  The typical number of transactions is an Average number of active transactions (those that have been purged from the queue but haven’t yet been finished).
  7. A typical reaction time is: Between the moment transactions are in the queue and the time they are processed, the average response time for transactions is measured in milliseconds.
  8. Percent time waiting: Transactions are waiting for service a certain percentage of the time (non-empty queue).
  9. Percent time busy: Percent Percent of time the disk is busy (transactions in progress).

Processes

Processes There are individual process counters in the processes section. In the counter definition window, choose the process identifier. The selection button opens a picker for the process identification.

  1. Process Memory Usage: Resident size (kb) in terms of process memory usage. the physical memory that a task hasn’t swapped out.
  2. Process CPU Time: The task share of the overall CPU time spent on CPU tasks since the last update.

Network (per interface)

Per interface, the network section counters are accessible. Select the interface name in the counter definition box outside of the wizard. The Populate button provides access to a network interface selector.

  1. Incoming bytes/s:  The amount of data that the network interface receives per second in terms of incoming bytes/s.
  2. Incoming packets/s: The quantity of packets that the network interface receives each second is known as the incoming packets/s.
  3. Incoming packet errors/s:  The number of damaged packets the network interface receives per second in terms of incoming packet errors/s.
  4. % Incoming packet errors:   % The percentage of damaged packets that the network interface receives is known as the inbound packet error rate (% Incoming packet errors = Inbound packet errors / Inbound packets *100).
  5. Outgoing bytes/s: The number of bytes the network interface sends out each second is known as the outgoing bytes/s.
  6. Outgoing packets/s:  The number of packets that the network interface sends out each second is known as the outgoing packets/s.
  7. Errors in outgoing packets: the rate at which the network interface issues broken packets in a second.
  8. % Outgoing packet errors:  The percentage of packets sent over the network interface that contain errors is known as the “% Outgoing packet errors” (% Outgoing packet errors = Outgoing packet errors / Outgoing packets *100).
  9. Packet collisions:  The number of packet collisions that the network interface has identified.

Tcp

  1. Incoming segments/s:  The total number of TCP segments received per second is known as TCP input segments/s.
  2. Segments completely duplicated/s Fully Duplicate Segments: The number of duplicate segments received each second. When a segment is received many times after one or more retransmissions, it is called a duplicate.
  3. % Segments duplicated:  The segments that are fully duplicated divided by the total number of segments received is the percentage of duplicated segments.
  4. Outgoing segments/s:  The number of TCP segments sent each second is known as the outgoing segments.
  5. Segments retransmitted/s: Number of TCP segments retransmitted every second, measured in segments/s retransmitted.
  6. % Segments retransmitted: Rebroadcast Segments / Outgoing Segments *100 = % Rebroadcast Segments, which is the percentage of rebroadcast segments.
  7. Resend Timeouts: How many timeouts cause a segment to be retransmitted.
Scroll to Top