Hi,

Just curious, do any of you out there change their polling interval from the standard 20 seconds? I'm thinking that the reason why some users get the so called "APB's" is that when some sort of process is running and then the BES server is polling the mail file, etc. I'm thinking if I increase the interval to maybe like 30 seconds, we can reduce the issue hopefully, etc.

I've changed polling intervals before...the only thing it does is delay redirection of mail. It's good for "balancing" mail flow patterns. Some of your more savvy users will notice a slight delay in their receipt of mail. As you increase the time (especially in high volume environment) you actually increase the amount of messages to route (redirect to handhelds). It would be mathematically impossible to determine at what instant an Inbox is polled simultaenously as a domino task is runned against it. In my case the APBs tend to be around early morning hours. We can turn off the tasks that run at that time or reschedule them (either in notes.ini or program doc). However you'll be messing around with tasks that do maintenance work, if not done, could cause more problems in the domino environment.
I've tried that reg hack several months ago...doesn't work in my case. It worked in the BES2.2 environment though.

Changing the polling interval is such an easy thing to do yet affects the entire environment. That is funny that people might notice a 30 second delay vs a 20 second delay... although I know that our guys (and myself) use the Blackberry as a new mail notification, since Notes notifications are so flaky!

RIM doesn't really recommend adjusting this value up or down. Don't know why adjusting *up* would be bad, but heard bad things about people changing it to 1 second and then wondering about their high network latency issues...

We have a very tech savvy group of individuals....some developed apps for Lotus and some actually trained some of the RIM guys (back when they actually listened...and their stock was 6.50CDN). It's amazing...when they first started they knew absolutely nothing about Domino/Notes.
Anyway...a couples seconds delay on the BES side could translate to 5-15mins. Worse when the wireless network is very busy between 9:00AM->2:30PM which sort of coincides with the Domino mail traffic. I learned to stop messing with the polling interval.

Can you explain how changing the polling from 20 to 30 seconds could translate into 5-15 minute delays? Not sure I follow how that might happen.

The BES2.2 polls the users' mail server at X secs intervals (not for Xsecs each interval).
When you increase the wait period (interval) before the BES polls the mail server again, each enabled user has received more messages in their Inbox pending redirection. The BES service has slightly more messages per user to scan than it would if at the optimized 20secs interval. Which by the way is arrived by, as was explained by a developer, a mathematical principle called "system optimization". Using 2nd/3rd order differentials.
The BES service also has to route these messages and check for retrys for devices not responding (similar to what the domino mail router does). Remember that each user is allowed only 5 messages on the wireless network and the queue is monitored by the BES service.
So if a user gets 5messages/min in an hour that user would have 300messages. Therefore, at 20sec intervals that user would have 100messages. At 30sec intervals that same user would now have 150messages. That 10secs has resulted in an extra 50messages. The wireless network will only accept 5messages/user (this is to prevent spamming on the network). Messages are sequentially tagged and handled by the BES service. So later messages will never arrive before earlier ones. It's technically impossible to route 150messages as fast as 100messages...given the randomness of size differentials. Mail routing is a time dependent task.
How long does a scan take...depends on the amt users + amt new docs/user (in the Inbox) + no filters/user.
Hence the reason a heavy mail user would tend to notice delays more frequently than a light user (especially if they have dual access to email client).
If you add network latency issues to the mix, it makes it a bit worse.

Sorry about the math...that should read 5messages/sec not per min, and in 1min a user will have 300messages.

Makes sense that as you handle the messages quicker, the network and all aspects of it are subject to less chunking/queuing and other overhead etc. Thanks for the explanation.

Interesting that they came up with the 20 second number, is it documented anyway on their site?

It was mentioned in the early stages of the BES2.0 release several years ago,in the Technical Overview docs. What was not described is "how the value" is determined. Unless you are a PP or BP, you wouldn't get the inside info.
PP: Platinum Partner
BP: Business Partner

i know, this is a very old thread, but i have one question. how does this thread depands on bes 4.0? same settings?