BlackBerry Enterprise Service 10
- BlackBerry Enterprise Server
BlackBerry uses Windows Performance Monitor to monitor many performance counters on performance testing servers and to verify that the tests avoid hardware resource bottleneck conditions that can invalidate the results. The following tables document some of the primary counters that should be tracked and guidelines for warning conditions. The guidelines refer to average values over periods of time. Infrequent short intervals of higher resource usage are generally acceptable.
|% Processor Use||- < 75%|
|Processor Queue Length||- < 1 per processor core|
Disk throughput capacity is critical for messaging servers and the BlackBerry Enterprise Server. One of the major causes of slow email message delivery is when one or more disks on a messaging server is over-utilized.
|% Disk Busy Time||- Not reliable, use % Disk Idle Time instead|
|% Disk Idle Time||- > 45%|
|Disk Transfers/sec||- Depends on disk speed, type, RAID configuration, cache characteristics|
- < 120 to 180 IOPS per disk spindle for 15 K RPM drives
|Average Disk Queue length||- Typically used for Direct Attached storage < 1 per spindle|
|Average Seconds per Read or Write||- Typically used for SAN storage|
- Messaging servers can be particularly sensitive to high latencies
- Average: Less than 5, 10, or 20 ms, depending on the application
- Spikes: Over 50 ms for several seconds can indicate performance issues
|Logical Disk Free Megabytes||- Often overlooked; if drives fill up, processing might stop|
Additional Note (re: Memory/Disk interaction): Paging might show up as high disk usage, but is actually a memory issue.
Network (typically WAN)
|Output Queue length||- < 1|
|Bytes Total per second||- Bandwidth limit depends on length|
- < 25% of the available bandwidth
Memory — Server
The server memory is a global resource for all processes.
|Available Bytes||- > 50 MB (In the Windows|
Memory — Process
You can monitor the memory of individual processes to determine a root cause if the server memory is being consumed.
|Private Bytes is the terminology used in the Windows Performance Monitor. In the Windows Task Manager, this counter is known as the VM Size (on Windows Server 2003 and older) or Commit Size (on Windows Server 2008 and newer) , and must be added as a column since it is not visible by default. It is not the same as the Mem Usage column in the Windows Task Manager. The Private Bytes or VM Size counter typically demonstrates whether a process has a memory allocation problem. Caches that grow slowly also build up this counter.|
|Virtual Bytes||This is the user mode address space of a process and is available in the Windows Performance Monitor only. It is sometimes called virtual memory, however, you cannot view it in the Windows Task Manager. This counter is not the same as the VM Size or Commit Size measure that is available in the Windows Task Manager.|
On 64-bit Windows systems, a 32-bit process that is large-address aware can address up to 4 GB.
Additional Note (re: Memory/CPU interaction): Processes that use Java or .NET technologies use Garbage Collection to manage memory. Low memory conditions may show up as high CPU in these processes.
By downloading, accessing or otherwise using the Knowledge Base documents you agree:
(b) not to copy, distribute, disclose or reproduce, in full or in part any of the documents without the express written consent of RIM.
Visit the BlackBerry Technical Solution Center at www.blackberry.com/btsc.