| Author |
|
people
Newbie
Joined: 25 March 2014
Location: United States
Online Status: Offline
Posts: 4
|
| Posted: 05 January 2015 at 12:19pm | IP Logged
|
|
|
Sometimes, when there are large number of emails in the pickup folder, the performance suffers. When we stop and start the service, it improves the performance. We had to do this several times in day. Why is this happening?
|
| Back to Top |
|
| |
Alex
AfterLogic Support
Joined: 19 November 2003
Online Status: Offline
Posts: 2206
|
| Posted: 05 January 2015 at 2:22pm | IP Logged
|
|
|
It's a kind of problem which needs detailed analysis of MailBee.NET Queue log file, examining CPU usage when sending becomes slow, fine-tuning of the configuration, and so on. There can be many reasons for it (for instance, throttling by the SMTP server which can limit the maximum number of messages per second it will relay after the client hits some threshold, restarting the service gives a break and the limit is removed). But, again, there can be much more reasons for it. Maybe there are many connections left (Windows can become slow if many sockets are opened and closed very often during the process life). In this case, sending more messages per single session may help. And so on.
Regards,
Alex
|
| Back to Top |
|
| |
MailBee.NET Objects 
MailBee.NET Queue 
MailBee Objects 
WebMail Pro PHP 
AfterLogic Aurora 
MailSuite Pro for Linux 
Unified Messaging Solution 
Search
Register
Login
Topic: Forces us to Stop and start service
Privacy policy |
Refund policy