[Resolved] Performance issues after adding more languages

Hallo,

In der Tat hatte ich nur mit einem Duplikat getestet.

Ich habe den Second Tier Support darüber informiert und werde mich wieder melden, sobald ich von dort eine Rückmeldung habe.

Mit freundlichen Grüßen
Andreas

Hallo,

Gern geschehen.

Sogar dann, wenn ich das Staging mit einem Standardtheme und alleine WC und WPML teste, sehe ich eine Ladezeit von 100 Sekunden, wenn wir das Produkt editieren und erneut speichern (allerdings keinen Error).

Ich habe den Second Tier Support darum gebeten, sich das nochmals genauer anzuschauen.

Sobald ich Neuigkeiten habe, werde ich mich wieder melden.

Mit freundlichen Grüßen
Andreas

Hello,

Wishing the same for you!

Best regards
Andreas

Hello,

Yes, for sure.

The private reply form is enabled again.

The second-tier support recommended adding the following snippet to the functions.php file of your Salient Child Theme:

add_action ('wp_insert_comment', 'test_remove_hooks0', 1, 10);
function test_remove_hooks0($var) {
	global $wp_filter;
	    foreach ( $wp_filter["wp_insert_comment"]->callbacks[100] as $key => $value ) {
		    if ( str_contains( $key, 'duplication_insert_comment' ) ) {
			    remove_action( 'wp_insert_comment', $key, 100 );
		    }
	    }
	return $var;
}

Could you please test this on your staging and let me know if this solves the issue?

Best regards
Andreas

Hello,

I would honestly say that this is fine, as a saving time of 8-10 seconds can be normal even when using only 4 languages.

The more custom fields and attachments a content has will extend the processing time of the queries.

You are using many languages and the fact that we are handling duplicates requires more DB queries than usual which for this loading time might sadly be normal in this case.

Do you have a saving time of about 30 seconds even without using the comment duplicate option?

If so, for now, I would like to ask for some patience, as we have already escalated this issue to the developers who are reviewing this issue - as mentioned earlier, we might consider excluding review duplication if the post comment duplicate option is enabled.

(we have an option for displaying reviews in all languages in WCML already)

Best regards
Andreas

Hallo,

Ich kann mich hier leider nicht mehr anmelden, weil der Nutzer wohl nicht mehr existiert.

Kannst Du mir bitte nochmals Zugriff, idealweise zur Staging Site, erteilen?

Das private Antwortformular ist erneut aktiviert.

Mit freundlichen Grüßen
Andreas

Hello,

Your site is now using 30 active languages - from those many custom languages.

I create a new product, left a review as admin, then duplicated the product into all 30 languages, and afterward edited and saved the product.

Take note that I already experienced a longer loading time when creating this original product and when leaving the admin review.

It took about 25 seconds to create the duplicates for all 30 active languages.

For a product without review creating the duplicates take about 17 seconds.

Editing and updating the original product took about 30-40 seconds for creating duplicates in 30 languages if the product has at least one review.

I get the same results, even when testing only with WooCommerce, WPML, and the Twenty Twenty One Theme.

Without WPML and only with WC and WCML the product updates in about 6 seconds.

If I enable WPML again and test with a new product that does not have a review but is duplicated into 30 active languages, the execution time on edit and save is taking me about 24 seconds - even without having any review.

This is clearly related to the number of active languages and the queries needed to create the duplicates and I would say at this point that this loading time is expected.

This means, the issue is clearly connected to the fact, that WPML needs to create duplicates in many languages and the fact that a review is placed on the product will even cause more queries to run, but a long execution time I do even see without reviews here.

Sadly, at this point, I am not able to confirm if this is somehow hosting-related, as I can not take a copy of the site for testing it on a virtual server, as Kinsta does not allow it.

What I can offer is setting up a local install with WordPress and migrating your database over there one more time for another test.

I would like to ask you for some patience on this matter.

Best regards
Andreas