CPU at 100% after Product Saved through Admin Panel

[ak429]

We've noticed that whenever a product is created and saved or edited and saved through the Magento Admin Panel, our CPU Utilization goes to 100%. Is this something that others have experienced? How have you resolved this issue? It can at time impact the user experience on our production server which is something we absolutely want to avoid. We are currently on the Magento Community Edition Magento ver. 1.9.1.0. 

[Damian Culotta]

Hi @ak429,

No, isn't the normal behavior but maybe you can share more details as:

• PHP version
• RAM
• # CPUs
• Have you some module using events to capture the save after of a product?

Maybe you can disable 3rd-party modules to check if the problem still persists?

[ak429]

Hi @Damian Culotta...thank you for your response. Please find the answers to your questions below. Looking forward to your thoughts. 

PHP 5.5.9-1ubuntu4.22 (cli) (built: Aug 4 2017 19:40:28) 
Copyright (c) 1997-2014 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2014 Zend Technologies
with Zend OPcache v7.0.3, Copyright (c) 1999-2014, by Zend Technologies

RAM: 4GB

CPUs: Dual Core

[ak429]

It does appear that saving a product from the magento admin panel is causing a mass reindex which is causing this problem. My understanding was that creation and save of a product from the Magento Admin Panel should only cause a SELECTVIE index update, NOT a mass reindex. Anyone have insights on this? I appreciate your help!

[Damian Culotta]

Which Magento version and edition are you using?

Can you disable 3rd-party modules?

[ak429]

@Damian Culotta we're using the Magento Community Edition ver. 1.9.1.0. We have a number of third party extensions installed. One is the Amasty Improved Navigation extension. My hunch is that this might be causing the problem. Your thoughts? 

[Damian Culotta]

Hi @ak429,

I can't answer that without checking the code (all the code of yoru store).

If you cant to be sure the easiest way is disabling that module and checking again. I guess you'll get the answer to your question in that way.