[funnyghost]

Hello All,

We are having a BB server.

Version: 4.1.6.14.
Only 272 users in the server
OS: Windows 2003 server R2, Standard Edition, Service Pack 2
Dual-Core AMD Opteron (tm)
Processor 8218 2.61 Ghz, 2:00 GB of RAM

Attached the screenshot of the BB server performance window.

**BB Monitoring tool is seperately configured in another dedicated server.
**Other than BB Monitoring tool, We also configured the BB server in the SCOM to monitor the server performance and service availability.

Issue:

Past 2 weeks we are getting alert stating "The 'BlackBerry Attachment Service' service is consuming excessive resource"

Like that for all the BB services,we are getting this alert. Daily atleast >100 alerts.

When I checked the BB service health in the SCOM server the handle count, processor time, thread count & working set are showing in warning state. Hence we are getting this alert.

Do anyone knows, why these BB services are consuming excessive resource ( I mean why the handle count, processor time, thread count & working set for these BB service are above the thershold limit)

Thanks/ Funnyghost.

[knottyrope]

Can you monitor it and find out in the BES logs what is going on when it happens?

Also have you installed any MR's for sp6?

[hdawg]

The resource utilization of these processes isn't excessive.

[funnyghost]

Yep already we have MR's for sp6.

[funnyghost]

Current Process: C:\Program Files\Research In Motion\BlackBerry Enterprise Server\BESAlert.exe
Current Process logged on as: DELUXE\Besadmin, Start Time: May 21 2009 13:26:39, Uptime (seconds): 902001
Current Process id: 1308
Computer Host Name: DSVPWM02, OS Version: 5.2, Build number 3790, ServicePack Major 2, ServicePack Minor 0
Processor Identifier: x86 Family 15 Model 65 Stepping 3
Processor Vendor Identifier: AuthenticAMD
Processor Name String: Dual-Core AMD Opteron(tm) Processor 8218
Number of Processors: 1
84 percent of memory in use.
Total size of physical memory: 2096584 KB
Size of physical memory available: 328112 KB
Size of the committed memory limit: 6977676 KB
Size of available memory to commit: 5407372 KB
Total size of the user mode portion of the virtual address space of the BES process: 2097024 KB
Size of unreserved and uncommitted memory in the user mode portion of the virtual address space of the BES process: 2073824 KB
Total HD bytes: 38658781184, Total free bytes = 14631071744
System up time: 10 days 10 hrs 36 mins 03 secs

[hdawg]

Seriously ... nothing is excessive here. Are you running into performance issues?

[funnyghost]

my management is asking, why we are getting the alerts?
NOTe: 84 percent of memory in use.

Subject: Alert: Windows Service Performance Issue Priority: 0 Severity: 2 Resolution state: New

Alert: Windows Service Performance Issue
Source: Deluxe Blackberry Attachment Service
Path: DSVPWM02.deluxe.com
Last modified by: System
Last modified time: 6/1/2009 6:24:10 PM
Alert description: The 'BlackBerry Attachment Service' service on computer DSVPWM02.deluxe.com is consuming excessive resource

Now my question is, how can i prove to my management BB service is not consuming excessive resource?

Please suggest/help.

Thanks/ Funnyghost

[hdawg]

You're getting the alerts because your monitors are triggering too low.

You can check out the Performance Benchmarking Guide to compare to tests RIM has done:

http://na.blackberry.com/eng/deliver...king_Guide.pdf

If you want to prove to your management call T-Support and ask them to validate it.

[funnyghost]

I have already have this pdf. But I am not sure, how to compare the testing for our BB server.

[TargetIT]

Throw another 1 or 2 gigs of RAM in there and call it a day. SQL will eat up 2 gigs if you let it.

[hdawg]

Adding memory isn't going to address the issue at hand. The server doesn't need more RAM, but rather someone wants an answer to why the server is using the current resources. Plus, if you add 2GB you're not going to get much benefit from the app perspective as it won't address more than 2GB of RAM anyway. ... unless you use a /3GB switch ... which I don't think is recommended in general for BES.

Like I said, your server is efficiently using resources ... its acting normal. If it seems abnormal it is because the alert parameters are not properly configured.

[TargetIT]

MSDE won't use more than 2, but the BES services and the rest of W2K3 will.

It just dawned on me though - you say you're running a dual core system but only one CPU is showing. Maybe there is something not quite configured on your box? Or did you switch it so it outputs everything on one graph?

[penguin3107]

Originally Posted by TargetIT

MSDE won't use more than 2, but the BES services and the rest of W2K3 will.

It just dawned on me though - you say you're running a dual core system but only one CPU is showing. Maybe there is something not quite configured on your box? Or did you switch it so it outputs everything on one graph?

I think you may still be missing the point.
You're making suggestions for addressing performance issues, when in fact, there are no performance issues.

The box appears to be performing just fine with the currently installed hardware.
It's the alerting that's flawed, and that's the point that hdawg is making.

[TargetIT]

Not at all, I'm quite aware of what he's trying to point out. However, when I see a box running down to 200 megs, I know for a fact that Windows is starting to swap out virtual memory to maintain that level and that will affect performance. Rather than arguing about what is and isn't a proper trigger level, I would rather throw a couple of sticks of RAM into the box and free up the resources. If I'm having the conversation with management and they ask how I resolved it, which is going to sound better to them: "I installed some memory and the performance issues subsided" or "I put a penny in the fuse box so it won't trip anymore". The latter may very well be completely logical and correct, but it's a long and tedious argument that I would rather avoid.

[hdawg]

unless you look at the perfmon counters and see it swapping excessively then you don't know it is.

Windows ALWAYS swaps ... unless you configure no page file.

... and no, the rest of the BES services won't use more than 2GB of memory. 32-bit system ... 4GB addressable memory limit ... by default 2GB to applications 2GB to system. If you do the /3GB boot switch you can allocate an additional gig ... but again, that is way past the point; the box is performing fine.