High server load due to cobby

The real cause is usually another, which becomes visible through cobby.

A high load on the Magento server can influence the shopping behavior of customers, e.g. through long loading times, which can lead to fewer sales. In this case, the system is often looked at superficially to find out what is slowing down the system in order to fix this as quickly as possible.
Often cobby or the Mash_Cobby_Mash2Controller then shows up in the php Analytics reports.

Please note that this is not the cause of the problem, but a symptom that only becomes visible through cobby.
Turning off cobby does not fix the problem.

Find the problem

Because cobby processes every product change (read more here), everything related to products, categories and attributes runs through the Mash2_Cobby_Mash2Controller and php Analytics reports.

To find and eliminate the real problem, it is first necessary to find out which products are processed, where and from whom the changes come and why. With the help of this article it is possible to find out by whom the product change was made.

Now, the username and the context should be known in order to narrow it down as much as possible. What should not be ignored is the time factor, because the time span must be observed in any case. If a lot of changes have been made within a few seconds, this is a sign that a script is running and affecting the system.

With your own agency and these new information, finding the cause will be easier.

Known causes

• an enterprise resource planning system that unnecessarily updates products without changes being present (sometimes even for products that are not present in Magento)
• extensions that trigger unnecessary events and/or are not programmed to be Magento-compliant
• scripts that make changes or are not optimized (no batch processing)
• cron jobs that are executed too frequently
• caches which are not built

It is best to discuss the cause with your own agency.