Back to Community Threads
[Beta] IIS worker process, crazy memory usage
Question asked by echoDreamz - 4/23/2020 at 10:05 PM
Answered
Latest beta, MAPI finally seems to be working without a crash, however, the memory usage is crazy...


Almost 7GB of memory used. We only have 1 Outlook install connected with 2 MAPI accounts. Normally our IIS worker is around 2GB in size. 
echoDreamz Replied
4/23/2020 at 11:06 PM
About an hour later, memory dropped back down to 2GB.
Same issue with memory here.
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)
echoDreamz Replied
4/23/2020 at 11:56 PM
It's now reduced down to around a gig. Though, I am not sure if the RAM usage is being caused by the exceptions being thrown by my other account. I've removed it from Outlook pending ST looking into the exception.
Tim Uzzanti Replied
4/24/2020 at 9:13 AM
Employee Post Marked As Answer
Yea, we keep trying to work around instabilities in IIS related to Threading / WCF / Garbage Collection.  We avoided crashes with that last build but we saw Garbage Collection wasn't working properly which we think we have found a solution for as well and will be in the upcoming version today.
Tim Uzzanti CEO SmarterTools Inc. www.smartertools.com
great Tim! You and your team are making an awsome work, hope that step by step you reach the final stage soon!
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)
echoDreamz Replied
4/24/2020 at 11:53 AM
Thanks Tim! While we dont mind increased RAM usage if it is beneficial, just wanted to check if it was unusual.
echoDreamz Replied
4/24/2020 at 10:15 PM
This is no longer an issue in the latest build. Memory usage is very much under control now.
Back to Community Threads

Reply to Thread

Enter the verification text
Related Knowledge Base Articles
500 Error After Upgrading to the Latest BuildSmarterMail > Troubleshooting
Deploying Rspamd For Use With SmarterMailSmarterMail > Server Configuration and Management
Controlling Memory for .NET Garbage CollectionSmarterMail > Server Configuration and Management
User's Disk Usage Doesn't Match Server PropertiesSmarterMail > Troubleshooting
Set up SmarterMail as an IIS Site in IIS 10SmarterMail > Server Configuration and Management