- Posts: 9
- Thank you received: 0
Kunena 6.3.7 Released
The Kunena team has announce the arrival of Kunena 6.3.7 [K 6.3.7] in stable which is now available for download as a native Joomla extension for J! 4.4.x/5.0.x/5.1.x/5.2.x. This version addresses most of the issues that were discovered in K 6.2 / K 6.3 and issues discovered during the last development stages of K 6.3
Note: Please go to the Kunena Dashboard after an upgrade so that the Kunena database tables are also updated.
Solved High CPU usage on J2.5 site
-Joostrap template (just minifying it now)
-Advanced Module Mgr
-Xtplorer
-Kunena
I've got caching on and Robots.txt is blocking all bots.
Latest CPU stats:
Jun 16 2012: (final stats)********** All extensions still running
joomla.org.au 4.82 1.22 0.0
Top Process %CPU 149 /usr/bin/php /index.php
Top Process %CPU 126 /usr/bin/php /index.php
Top Process %CPU 124 /usr/bin/php /index.php
Jun 17 2012 (partial stats, 06 hours):********** All extensions turned off, including Kunena
joomla.org.au 0.42 1.03 0.0
Top Process %CPU 27.0 [php]
Top Process %CPU 0.3 httpd [joomla.org.au] [/administrator/templates/bluestork/images/menu/icon-16-mess]
Top Process %CPU 0.1 httpd [joomla.org.au] [/templates/system/css/error.css]
Jun 17 2012 (full day): ********** Kunena turned back on part way thru day
joomla.org.au 1.49 1.00 0.0
Top Process %CPU 93.0 /usr/bin/php /index.php
Top Process %CPU 56.5 /usr/bin/php /index.php
Top Process %CPU 55.0 [php]
Jun 18 2012 (partial stats, 03 hours into the day): ***** Kunena back on
joomla.org.au 1.67 1.27 0.0
Top Process %CPU 69.0 [php]
Top Process %CPU 0.3 httpd [joomla.org.au] [/components/com_kunena/template/default/images/icons/stats.]
Top Process %CPU 0.2 httpd [joomla.org.au] [/media/kunena/avatars/resized/size36/users/avatar63.jpg]
Please Log in or Create an account to join the conversation.
To me it looks like Kunena isn't the issue. Here's the total resource usage during the last minute or so according to your stats (100% = full load):
All extensions = 482% (bad)
Kunena = 149% (still ok)
Don't look individual process CPU time as they are supposed to be as high as possible to be able to serve pages faster. Look the three numbers above: 1.49 1.00 0.0. Those tell you average CPU load now, during the last few minutes and long average. One CPU = 1.00, except on virtual servers where the number means the time that's allocated to you.
So your other extensions are causing almost 3x load compared to Kunena. It doesn't mean that the extensions are slow, but it points to me that the server resources allocated to your site run out and saturate. The effect is the same as in traffic jam: once the limit is reached everything slows down and take 3-5x more time. If situation doesn't get any better, after a few minutes load gets up to 50-100 and every page load takes something like 30-300 seconds.
Your main issue is that your server just isn't powerful enough to run a busy Joomla site with your current configuration. Part of that can be fixed by optimizing Apache/MySQL configuration and removing all extensions that you really don't need. Also upgrading to Kunena 2.0 should help, as it caches some data and should therefore use less resources.
Please Log in or Create an account to join the conversation.
Thank you for your detailed explanation. Much appreciated.
I understand what you mean now.
As almost all of our extensions are still turned off, and I dont have access to tweak Apache/MySQL, what I draw from this is that we've outgrown our hosting and should move on up to something beefier.
Thanks again
Dex
Please Log in or Create an account to join the conversation.
Blue Eagle vs. Crypsis reference guide
Read my blog and
Please Log in or Create an account to join the conversation.
Thanks to everyone who has worked so hard to get this new release out. You rock!
And thanks to Sozzled and all of you who have helped with ideas.
cheers
Dex
Please Log in or Create an account to join the conversation.
Do this before a new users (who has not yet attached something to their post) attaches something or you will get HTTP 500 errors and the site will be locked out (backed, too). This is an important fix (properly corrected in K 2.0.1 to be released shortly) and necessary for all K 2.0.0 sites running on J! 2.5.x.
Do it now, please.
Blue Eagle vs. Crypsis reference guide
Read my blog and
Please Log in or Create an account to join the conversation.
I thought that most of the optimizations have little or no impact if there are only thousands of posts, but I had no idea on how wrong I was! Maybe shared hosting environments have some limitations that are unique to them and our optimizations work also in those environments.
Nice! That only will make K2.0.1 the best release ever.
Please Log in or Create an account to join the conversation.