• Resolved Lalit Jindal

    (@lalitjindal)


    Hi Guys.

    Do you guys know what this error is about in the log?

    Thank you

    //WordPress-Datenbank-Fehler Deadlock found when trying to get lock; try restarting transaction für Abfrage DELETE FROMwp_optionsWHEREoption_name= 'wphb_cache_preload_batch_dd77cc194f9fa63da8b99e334bb7116a' von do_action('wp_ajax_nopriv_wphb_cache_preload'), WP_Hook->do_action, WP_Hook->apply_filters, Hummingbird\Core\Modules\Caching\Background_Process->maybe_handle, Hummingbird\Core\Modules\Caching\Background_Process->handle, Hummingbird\Core\Modules\Caching\Background_Process->delete, delete_site_option, delete_network_option, delete_option

    //

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Dimitris – WPMU DEV Support

    (@wpmudev-support6)

    Hello there @lalitjindal

    It seems like related to the Preload caching options in Hummingbird Page Caching.

    Could you please deactivate any preloading options and check again?

    Also, if using these pre-loading options, please do keep the Clear full cache when post/page is updated option disabled.

    Looking forward to your results.

    Thank you,
    Dimitris

    Thread Starter Lalit Jindal

    (@lalitjindal)

    Thanks Dimitris

    “Clear full cache when post/page is updated” was already disabled.

    I’ve disabled preloading. This seems to solve a couple of problems I was having.

    I guess preloading only affects the load time of the first visit to the page not subsequent users? I’ll keep it off.

    I have another question about Asset optimization:

    Should the preload asset option be used on CSS that has been moved to the footer? https://i.imgur.com/oVtn0oq.png

    And should it be used for JS that has been moved to the footer or loaded after the page load? what about when an asset is combined? https://i.imgur.com/wibSmsa.png

    In other words, when is it appropriate to use asset preload and when should it be completely avoided?

    Thank you so much

    Plugin Support Patrick – WPMU DEV Support

    (@wpmudevsupport12)

    Hi @lalitjindal

    I guess preloading only affects the load time of the first visit to the page not subsequent users? I’ll keep it off.

    The preload will cache the page when the cache is flushed but in some cases can cause high server usage based on how many time the pages get flushed, however, it is fine to keep disabled.

    Should the preload asset option be used on CSS that has been moved to the footer? https://i.imgur.com/oVtn0oq.png

    No, you only preload important files for example Theme CSS file.

    And should it be used for JS that has been moved to the footer or loaded after the page load? what about when an asset is combined? https://i.imgur.com/wibSmsa.png

    Yes, you can use the combine and load after page, same as moving to the footer.

    In other words, when is it appropriate to use asset preload and when should it be completely avoided?

    We have a great guide for Assets Optimization at: https://wpmudev.com/docs/wpmu-dev-plugins/hummingbird/#asset-optimization

    Best Regards
    Patrick Freitas

    Thread Starter Lalit Jindal

    (@lalitjindal)

    Yeah, I’ve already gone through the doc. Thank youy

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘database error.’ is closed to new replies.