⌛ Editor V4 generates very large Atomic Cache Validity database entry #32220
Replies: 5 comments 1 reply
|
Hi @TadeasKula! Thank you for sharing this information! We are investigating this information, but so far we could not reproduce it on our side. Usually for this kind of report we ask users to submit a 🐛 Editor V4 Bug Report. This way we can gather more information such as the Elementor System Info, and try to reproduce the issue on our end with more accuracy. Would you mind elaborating a little more about your issue? We are looking for the following information:
Looking forward to hear from you! 🙏 Kind regards |
|
Hi @TadeasKula! We are investigating this issue, and having a hard time to reproduce it. Would it be possible for you to copy the contents of this database entry and share it in a text file with us? There is no sensitive data in this entry, so it's safe to share it here. We need to investigate this further and having this information would help us a lot! Also, if you could please share a little more about the site you are testing this with, it would be awesome! We're looking to understand the following:
We want to ensure this is not a problem that could affect production sites once V4 is released. Your help will make Editor V4 be more stable! Thank you in advance! 🙏 |
|
Hey @TadeasKula, we've been working on changing how we handle the cache validity, and soon this won't be a problem anymore. But we still would love to hear your feedback regarding the other comments I made. Please let me know. Kind regards! |
|
Independent confirmation at larger scale, plus three findings that compound Environment: Elementor 4.2.3, WP 7.1, PHP 8.4, nginx, 3 dedicated cores. 1. The cost multiplies when a theme fires the style hooks per loop item.
2. The write path has no dirty check. 3. Dose-response (same URL, load-verified idle server):
Deleting the options is only transient — they rebuild within a day and the Our hosting provider's independent forensics over 18 hours: 1,932 requests Theme-independent reproduction. With only Elementor + Hello theme active for ( $i = 0; $i < 40; $i++ ) {
do_action( 'elementor/post/render', $template_id );
do_action( 'elementor/frontend/after_enqueue_post_styles' );
} |
|
I got this on a site now. The solutions was to disable the new Atomic Editor. Isnt this fixed by now? |
Uh oh!
There was an error while loading. Please reload this page.
Description
Extremely large elementor_atomic_cache_validity-local with autoload had to be forced to off through db cleaner. It got to a point where the whole wordpress stopped functioning.
Agreement
All reactions