2017-12-28 You can help protect yourself from scammers by verifying that the contact is a Microsoft Agent or Microsoft Employee and that the. Tell us about your experience with our site. GLIPPIP Created on December 28, 2017. SOLVED Outlook high CPU usage Split from this. You did an amazing job EXCEPT that this is a forum for Outlook for Mac, not. 2018-5-17 Microsoft Windows Search Indexer process (and perhaps related processes) suddenly begins using too much of my CPU, something that happens irregularly but often. I much appreciate any suggestions/help that you can offer me.
One of the major issues most users have with Outlook is the fact that it gets really slow and eats up a lot of memory on their systems. Mac powerpoint pencil. I have a 1.5 GB Outlook file, but Outlook runs fast and doesn’t hog all the resources on my computer! Why?
Well, it’s because I optimize my Outlook by doing a few routine tasks to make sure it stays clean and slim. Instead of dealing with Outlook crashes, crazy error messages, memory hogging or wasting time waiting for Outlook to load, why not follow my advice below to make Outlook fast and responsive.
One thing you want to understand about Outlook is that it’s completely run from a database. All your emails, tasks, calendar items, business contacts, etc. are stored in a database file. To reduce memory usage and make Outlook fast, that database needs to be small and optimized.
Reduce Outlook Memory Usage
Rule 1. Firstly, make sure you have AutoArchive turned on in Outlook. You’re probably never going to look at those emails from 5 years ago again are you? Instead of having thousands of emails in your Inbox, AutoArchive will move the older ones to a new PST file and keep your current PST file slim. You can always find those older emails later by doing a search.
Click on File and then click on Tools and then Mailbox Cleanup. You’ll see several options as shown below. I would check the mailbox size and if it’s anything over 500 MB, you should turn on AutoArchive or delete any emails that are taking up a large amount of space. Also, make sure to empty out the deleted items folder afterwards as that still takes up space.
It’s also worth noting that you have to do this for each mailbox you have setup in Outlook. That’s why it’s a good idea to turn on AutoArchive because it will take care of it automatically without any intervention.
If you don’t want to do that, at least move all older emails to another folder so that Outlook does not have to load thousands of emails every time it comes to the Inbox, thus causing higher memory usage.
Rule 2. Make sure you are only using essential add-ins for Outlook. A lot of programs love to install add-ons to Outlook automatically, such as Adobe, EverNote, Wunderlist, etc. Even Microsoft adds a bunch of stuff that I normally disable like Skype, OneNote, SharePoint, etc.
Too Many
If you don’t use them, get rid of them! They have to be loaded into memory when Outlook is started and they make the program slower also. To actually disable an add-in, you have to select COM Add-ins in the combo box at the bottom and click Go. Another window will popup and you can uncheck the items you don’t want.
Rule 3. Outlook comes bundled with the Speech and Handwriting Recognition features that are a part of Windows. If you don’t use this, disable it so that it doesn’t load every time Outlook starts. It will also prevent your system from scanning your emails, etc.
You can go to Control Panel, Speech Recognition and then click on Advanced Speech Options.
Under User Settings, uncheck the Review documents and mail to improve accuracy option.
Rule 4. Use a different program for RSS feeds and Internet calendars. Yes, Google Reader was great and now that it is gone, why not use Outlook to manage your feeds right? Bad idea! There are still many good online and offline RSS readers that you can use other than Outlook.
Outlook just wasn’t designed to handle RSS feeds all that well, so anything more than a couple will slow down Outlook. You can use Google Calendar for any Internet calendars you want to follow.
Rule 5. For some reason, people forget about their spam and trash folders. Empty them out! Someone like me gets hundreds of spam emails a day! That’s all stored in the Outlook database and slows it down. Empty your spam folder and your trash folder often.
GoToHeader will not take you to the header unless you are already in the footer. Microsoft word shortcuts pdf.
Rule 6. Compact your PST file every once in awhile. You can do that by going to File, then Data Management. Next click on the PST file and choose Settings. Then click the Compact Now button.
In newer versions of Office, you need to click on File and then Account Settings. Click on the Data Files tab and double-click on the data file you want to compact.
Outlook will do this automatically in the background, but only runs when your computer is Idle and Outlook is open. Sometimes this situation never comes up, so it’s good to do it manually once in awhile.
Rule 7. If you have really large Outlook files and search indexing is enabled, it could be causing massive slowdowns in Outlook. It may be a good idea to disable search indexing for Outlook until you need it or delete and rebuild the index in case. In any case, you should reduce the size of your main data files to make the index smaller.
Just click on Start and then type in search. Click on the Change on Windows searches option to remove Outlook from the search index.
Rule 8. Another big slow down for Outlook is any kind of anti-virus program that scans all your emails. Now this is very useful if you are someone who is prone to clicking on malware links or being spoofed by fake emails. Unfortunately, even the savviest of users sometimes get tricked, so the extra protection is helpful.
However, depending on the anti-virus program, it can really make things very slow in Outlook. If you are having this issue, it’s a good idea to turn off the anti-virus for Outlook and see if the problem goes away. If it does, you should consider a different program that is more efficient with the scanning.
Rule 9. This tip only applies to Microsoft Exchange accounts, so it won’t work for POP or IMAP accounts. Basically, you want to enable Cached Exchange Mode, which means the emails will be stored locally and accessed faster.
Go to File, Account Settings and then double-click on the email account under the Email tab. Check the Use Cached Exchange Mode box.
Hopefully, these actions will reduce your Outlook memory footprint and make it run faster! Also, make sure you install the latest updates and service packs for Office and Windows as these tend to help with performance and memory leak issues! Enjoy!
100% CPU issues seen recently due to high number of CPU. Max recommended CPU is 24
CPU is usually consumed by mapihttp module.
You will find below Resolution and Further details on the symptom and troubleshooting.
Resolution :
---------------
When there is too much CPU , more CPU time is spend due to minimum number of threads per CPU and synchronization named Contention
Exchange/ .net is not designed/optimized for so much CPUs and this is not following Exchange architecture recommendations.
There is a great article on Exchange dev team on this subject:
https://blogs.technet.microsoft.com/exchange/2015/06/19/ask-the-perf-guy-how-big-is-too-big/
Such problem and far more can be avoided by following design recommended named Preferred Architecture, or requirement calculators which integrate this maximum CPU number and provide further details to get best performance.
In most case the issue can be mitigated by disabling hyperthreading which is not recommended on Exchange and double artificially the number of CPU triggering this problem.
When it is physical CPU without hyperthreading , there are sometimes hardware options to disable part of the CPUs in order to avoid exceeding max number of CPU recommendation.
There is also a .net optimization for these contention generated by high number of CPU :
.net fix KB3146718 (Web Installer) or KB3146717 both contains this optimization.
Choose one package or the other depending if you need a web installer version or not
For applying these hotfixes , it is also recommended to apply CU13 or upper : http://technet.microsoft.com/en-us/library/ff728623.aspx
Such issues are fixed by applying this .net fix and disabling hyperthreading which reduce as well the number of CPU.
Further details on symptom and troubleshooting:
--------------------------------------------------------------------
Generic troubleshooting steps for 100% CPU is to check which process consume the CPU.
This can be seen from task manager during the problem or using daily perfmon logs stored under MicrosoftExchange Server V15LoggingDiagnosticsDailyPerformanceLogs
In most case I have seen, the process consuming most CPU in case of too much CPU is the w3wp.exe running MSExchangeMapiMailboxAppPool linked with mapihttp module.
c:windowssystem32inetsrvw3wp.exe -ap 'MSExchangeMapiMailboxAppPool' -v 'v4.0' -c 'C:Program FilesMicrosoftExchange ServerV15binMSExchangeMapiMailboxAppPool_CLRConfig.config' -a .pipeiisipm93b74187-ee0a-4645-9295-38cfcbed72a4 -h 'C:inetpubtempapppoolsMSExchangeMapiMailboxAppPoolMSExchangeMapiMailboxAppPool.config' -w ' -m 0
Tools to trace further causes of 100% CPU are usually Perfview or xperf trace as they help to narrow down the functions consuming most CPU.
Microsoft Outlook Using Too Much Cpu Machines
In these trace , you will see clr.dll!AwareLock::Contention the stack for main CPU consumption
Another way to trace high CPU is using dumps .
In these dumps , you will see lots of threads waiting on clr!AwareLock::Contention
Microsoft Outlook Using Too Much Cpu Machine
00007ffee4b70c6a ntdll!ZwWaitForMultipleObjects+0xa
00007ffee1f913ed KERNELBASE!WaitForMultipleObjectsEx+0xe1
00007ffed8e38976 clr!WaitForMultipleObjectsEx_SO_TOLERANT+0x62
(Inline) clr!Thread::DoAppropriateAptStateWait+0x45
00007ffed8e3877a clr!Thread::DoAppropriateWaitWorker+0x1d0
00007ffed8e38591 clr!Thread::DoAppropriateWait+0x7d
00007ffed8e3883d clr!CLREventBase::WaitEx+0xc0
00007ffed8e53ed6 clr!AwareLock::EnterEpilogHelper+0xc6
00007ffed8e53dea clr!AwareLock::EnterEpilog+0x62
00007ffed8e54521 clr!AwareLock::Contention+0x1e3
00007ffed8e54293 clr!JITutil_MonContention+0xaf
00007ffed769bc35 mscorlib_ni!System.Threading.TimerQueueTimer.Fire()+0xc5