Have you checked your spool service to see if any messages are stuck in the spooler??
I had the same and deleting mails from the spool made the server clam down.

Hello Trydon,

Absolutely.

Since 1st May 2023, we have > 50%.

On the afternoon of 1st May, due to a MAPI Problem, we had to re-sync one Mailbox on 3 PCs via MAPI (shared mailbox), then in the same time two other users with MAPI had to re-sync. So therefore just five (5) MAPI syncs, we had > 90% CPU on an 6 Core >4GHz Machine.

And "no", there is nothing in the spool service:

Do you have any errors showing up in the Errors logging or any of the protocol logs? You may also find relevant exceptions in the Event Viewer in Windows.

Hello Kyle,

Do you have any errors showing up in the Errors logging or any of the protocol logs?

--> nothing unusual

You may also find relevant exceptions in the Event Viewer in Windows. 

--> nothing unusual

Right now, Zach Sylvester told me that I should upload the ZIP File from "C:\Program Files (x86)\SmarterTools\SmarterMail\Service\Settings\Profiling" to my Emergency Ticket "244-[left-blank]-0B16".

I don't know if you want to go back to Zach for this issue.

We have not noticed any CPU spikes or issues with this build.

No CPU issues here...

FYI - after a reboot, the high CPU load was gone (yesterday).

And right now, I have a custom build installed for another reason, so I cannot go further because the situation has changed.

Regards,

Josip

Yes, was monitoring and intending to post. We've been seeing CPU 50%-70% +

We are suspecting it's the Outlook/MAPI clients syncing or constantly re-syncing since all the Outlook clients constantly are reporting "Updating email@domain.com... Updating Inbox.... Connected to: Microsoft Exchange"

They seem to always be "Updating"

CPU usage has gone up for sure, maybe reindexing? It's not catastrophic or anything, but we are seeing higher avg usage.

Hello Everyone, 

Thank you for your input here. We have a custom build that we have been testing and it seems to fix some high-resource issue scenarios. 
Indexing definitely uses a ton of CPU the indexing settings that I recommend using are as follows. 

 
But the issue looks like it could be related to some MAPI behaviors so there are going to be some fixes in the next release. If you'd like to help us validate the fix feel free to open a ticket(If you haven't already).

Thanks, 

Zach Sylvester  thanks for the Indexing optimization tip. Awesome.

But we think these CPU and Memory issues are related to Outlook. If we close down several of our Outlook clients. The CPU drops. Re-open, the CPU rises. Re-syncing users only temporarily lowers CPU. It builds back over time.

Hey Michael, 

We think it's related to Outlook as well. The protocol that we observed the issues with was MAPI. Have you found that another protocol is having issues too?

Thanks, 

Hello Zach,

your configuration under Manage->Troubleshooting is something that we all should set or just for that build?

Thanks!

By using that suggestion on 8517 our memory usage jumped 2,3GB upwards....

More spiky CPU use but not anything critical.
Edit: Upped it again to 10 threads and 10 seconds in the queue. Didnt change the 25.000 setting. Memory dropped 1GB instantly.