Keyword

MAX_EXECUTION_TIME change in version v2.11.20240212

  • sizu
  • sizu's Avatar Topic Author
  • Offline
  • Junior Member
More
3 weeks 6 days ago #181573 by sizu
Hi, 
I'm not sure which are the benefits of this update related to MAX_EXECUTION_TIME in the code that can be seen in github.com/getk2/k2/commit/0e47d272244cf74fcd56fc2d25357a3ee48af327
Can anyone explain me if there is any drawback I should consider before updating to this version?

Any help would be very appreciated!

Please Log in or Create an account to join the conversation.

More
3 weeks 6 days ago #181574 by JoomlaWorks
Replied by JoomlaWorks on topic MAX_EXECUTION_TIME change in version v2.11.20240212
This is a MySQL/MariaDB hint.

It's useful because it instructs MySQL or MariaDB to place a limit on long SQL queries, typical in lists of items like categories, tags, search results etc.

Such lists (= the itemlist view in K2) can be abused by crawlers, bad actors etc., so it's a nice way to protect the health of your database. How do we know? Well, only because the highest traffic sites in the world are built with K2 and NOT Joomla's com_content.

And this is reason #385739485 why K2 kicks ass compared to poor old Joomla, whose trajectory is that of a falling satellite (hint: will it crash or burn first?).

We got big plans for 2024 for K2 but my mouth is sealed ;)

Fotis / JoomlaWorks Support Team
---
Please search the forum before posting a new topic :)

Please Log in or Create an account to join the conversation.

  • sizu
  • sizu's Avatar Topic Author
  • Offline
  • Junior Member
More
3 weeks 5 days ago #181577 by sizu
ok, thank you so much for your fast response!

We got big plans for 2024 for K2 but my mouth is sealed ;)

I'm very glad to hear it! :)

Please Log in or Create an account to join the conversation.


Powered by Kunena Forum