[Résolu] Very slow query

[Auteur]

Publications

[jesusM-6]

Hello,

I have a problem with the page loading time.: hidden link
It takes almost 8 seconds to load.
Query monitor shows that I have 11 slow queries. I have installed Litespeed cache.
This page will be updated, approximately once a week.

Any suggestions on how can I improve the loading time? Thanks!

[Minesh Supporter Languages: Anglais (English ) Timezone: Asia/Kolkata (GMT+05:30)]

Hello. Thank you for contacting the Toolset support.

view's load time is depend on the server resources like CPU, ram as well as hosting.

I see you are using the nested views and the amount of data you are retrieving seems causing the issue as there are hundreds of posts are listed using the nested views.

Please check the following Doc that may help you:
=> https://toolset.com/documentation/legacy-features/views-plugin/how-to-use-views-parametric-search-on-large-sites/

[jesusM-6]

I have tried to fix the problem as follows:

Force to cache the 3 nested views with the attribute cached="force":

[wpv-view name="secciones-carta" cached="force"]
--[wpv-view name="contenido-de-cada-seccion-de-la-carta" cached="force"]
----[wpv-view name="alergenos-del-plato" cached="force"]

Now the three views are cached on server and the page where I display de views load fast.

But the problem comes when I modify something using a front end form to update a post. The view does not display the changes.

What can I do to clean the cache after update any post in the view ?

Thanks

[Minesh Supporter Languages: Anglais (English ) Timezone: Asia/Kolkata (GMT+05:30)]

The value for cache attribute for the view's is either On or Off as you can see with our Docs:
=> https://toolset.com/documentation/programmer-reference/views/views-shortcodes/#wpv-view

I'm not sure from where you find the value cached="force". By default view's cache attribute value is On.

Here is how you can enable-disable cache using the filter hook: wpv_filter_disable_caching
=> https://toolset.com/forums/topic/some-block-settings-are-no-longer-work-after-a-simple-page-refresh/page/2/#post-1514623