Magento 2.3.3 Cronjob use too much CPU source

[Yuwei9291]

Preconditions (*)

1.nginx, mysql5.6, php7.3, composer install magento 2.3.3
2.finish all the settings and set 3 cronjobs following the official document.

Steps to reproduce (*)

1.use top command to monitoring the task cpu usage.
2.run php bin/magento cron:run and check the cpu usage.

Expected result (*)

1. Smooth CPU usage, dose not cause the long time loading.

Actual result (*)

1. long loading time because of the high CPU usage(Clean Magento 2.3.2: 1s
   Clean Magento 2.3.3: 3.5s)
   

CPU usage record by panel

CPU usage

[m2-assistant]

Hi @Yuwei9291. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@Yuwei9291 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[Yuwei9291]

CPU Monitoring info

[jorgb90]

Same issue here #25593

[m2-assistant]

Hi @engcom-Charlie. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

✅ Confirmed by @engcom-Charlie
Thank you for verifying the issue. Based on the provided information internal tickets MC-28949 were created

Issue Available: @engcom-Charlie, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[interequipment]

Having same issue. (upgraded from 2.3.1 to 2.3.3)

[Jilco]

Is there a solution or work around? My CPU stays at 100%...

[atastycookie]

Hello,

Any updates or workarounds? Our "load average" is ~40.6 on the clean installations

[Jilco]

Update, i was google "attacking" my site for some reason, they indexed 159.000 pages a day at once...

Adjusting robots.txt to index less was the sollution

[vincentteyssier]

Hi, when you run di:compile the cache gets disabled somehow.
Even if cache management shows green in the admin panel, it is set to 0 in the back end.
Run php bin/magento cache:enable and cron will run with same performances as 2.3.2

[XstraAI]

Had a similar issue and tracked it down to an AJAX Layered Navigation module. Disabling the module resolved the issue.

[roni-sooryen]

Seems like this issue is able to fix this problem #26507

[driskell]

#28007 can help with high CPU as it removes some deadlocks that prevent cron schedule table from being cleaned. It can also fix things stuck in running status.

[magento-engcom-team]

Hi @Yuwei9291. Thank you for your report.
The issue has been fixed in #28007 by @driskell in 2.4-develop branch
Related commit(s):

• aa12503923ac994873724ecaa759e1eb14b318dc
• b0b72b0f8486ca119015e84b7786dfab13d2e475
• 315bd3af8c5ed3dd711abd40db9a163b0c953855
• 96029b55f7cd00b58967637aedac67ddd1767bad
• 7df183b6c6bc3f57f0c3d29d279c3c6d631cf455
• 68d679b7bd7d371c5266d4803f03f204893f7af2
• a90161907aedae371cb307759b685cc254efe2d8
• dda5c72c9303f9476ce7041743c87079cada87f6
• 4d4fa685c0b507b510ad899f5afe94bd6c836115
• e95d2fefefb62150e566f000a4a17f58f6716af5
• 916bc93138f7a81f65c2e8b5069eeb0f35fceb43
• edd77531f8847f7b13dbaca9aefa315ba4aa5e57
• e70027f838f766b816bd1f7063514c1a9caf7a20
• 92dc76438063e68f7523d5ab036a57d7faf7bc03
• d1b22ff825052d836b56f8ce33760d42b2241980
• a76482c4614a7660ab2d324ca4c086f66906c701

The fix will be available with the upcoming 2.4.3 release.