Thanks wjleong,
1. I didn't want to sign up for the Akismet API key that is why I am not using Akisment.
4. I might remove Google Analytics Dashboard as I am not really 'using' it, will do some more checking. It has these tiny charts that shows how many visitors I had for each article when I use the WP control panel to view all posts. That was very helpful.
The others, well I have not checked out Jetpack and may need to see how it works for others and a review. As for the 3 caches W3 Total cache, PHP Cache and Widget Cache, as I have put in a lot of work analyzing their performance for speed of page download to the visitors PC, I won't replace them with Jetpack just yet. Most of my articles have 7 to 14 photos 448x336 pixels per article so caching them on the server side did help a lot.
As for 1-click Retweet/Share/Like that was the only plugin, at that time when I was looking, that had a nice row of buttons for the top or bottom of the page. Many have floating buttons that keep irritating me. I only wanted buttons at the bottom of the page so that after a visitor has read the article they could decide if they wanted to 'like' or 'share'.
But that does not explain why on January 11th 2012 when there was a flood in Chicago the CPU usage went to 15%. They had blocked a whole range of IP addresses, not just mine, on and off. The servers could not be accessed most of the day, which means that the CPU's were idling, which means the CPU usage should have dropped to almost ZERO %.
I used to have high CPU usage on another site - different hosting account, but the third party software developers are changing their code to reduce the CPU usage.
Some data:-
Awstats
Day Number of visits Pages Hits Bandwidth
1-Nov-12 978 3,818 7,208 183.80 MB
2-Nov-12 972 3,253 6,493 172.91 MB
3-Nov-12 854 3,170 6,331 167.64 MB
4-Nov-12 964 3,960 7,695 213.11 MB
5-Nov-12 956 3,778 7,777 158.86 MB
6-Nov-12 1,022 5,138 11,288 169.77 MB
7-Nov-12 985 4,849 7,182 140.03 MB
8-Nov-12 947 3,773 6,587 158.01 MB
9-Nov-12 1,038 3,852 6,431 143.28 MB
1-Feb-13 796 3,114 5,209 123.96 MB
2-Feb-13 789 2,537 4,421 117.15 MB
CPU Data
Day CPU Time (s) Execution Time (s) CPU Usage Average memory Processes
1 1,168.29 40,964.88 3.38% 4.58 MB 2359
2 1,075.33 37,470.76 3.11% 4.60 MB 2191
3 971.84 35,145.59 2.81% 4.60 MB 1986
4 1,084.36 39,425.82 3.14% 4.60 MB 2247
5 1,341.44 44,232.04 3.88% 4.63 MB 2616
6 693.72 24,212.21 2.01% 4.61 MB 1443
7 1,874.62 47,205.26 5.42% 4.61 MB 2688
8 1,239.65 40,259.80 3.59% 4.60 MB 2301
9 1,208.61 39,445.58 3.50% 4.60 MB 2297
1 2,832.20 37,159.93 8.20% 4.63 MB 2210
2 2,211.90 26,269.64 6.40% 4.59 MB 1526
Analysis of above data:-
Day Test Execution Test CPU Test Processes Processes/CPU sec
1 2.02
2 37,692.54 1074.965059 38,047.50 2.04
3 33,856.22 971.600418 33,964.82 2.04
4 39,273.01 1085.970676 39,764.42 2.07
5 48,717.26 1339.909809 45,900.29 1.95
6 22,914.02 694.9212371 24,398.64 2.08
7 65,288.65 1870.62806 45,102.16 1.43
8 31,266.95 1241.676347 40,408.97 1.86
9 39,250.50 1208.572423 40,189.81 1.90
1 92,415.36 2831.600571 37,951.56 0.78
2 29,002.87 2210.497561 25,658.85 0.69
Test execution is calculating how many seconds for the day based upon previous day execution time and CPU % and todays CPU %. The figures are way off. This means that Execution time is not related to CPU usage.
Test CPU shows projecting todays CPU time (s) based upon yesterdays CPU seconds and %. The projections are very close ie there is a correlation.
Test Processes is projecting todays Execution time based on yesterdays execution time and number of processes. The figures are very close which means that execution time is related to the number of processes running.
Porcesses/CPU second is showing how many processes run per CPU second used. This clearly shows that in November 2012 the server was able to run 2 processes per CPU second but by February 2013 the figure has dropped to 0.78 processes per CPU second. The only the only thing I have done to WORDPRESS was to upgrade it over the months since March 2012. All other plugins had been installed before August 2012. In February or end Jan I had upgraded WP to ver 3.5.1 and SEOPressor to v5 and I implemented browser caching in my .htaccess file
## EXPIRES CACHING ##
<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType image/jpg "access 1 day"
ExpiresByType image/jpeg "access 1 day"
ExpiresByType image/gif "access 1 day"
ExpiresByType image/png "access 1 day"
ExpiresByType text/css "access 1 day"
ExpiresByType application/pdf "access 1 days"
ExpiresByType text/x-javascript "access 1 day"
ExpiresDefault "access 1 day"
</IfModule>
## EXPIRES CACHING ##
Browse caching is very usefull and powerful technique if your images are repeated across all your pages. It saves a lot of back and forth communications between server and client and reduce content download so pages appear almost instantly on the client side. But one drawback of browser caching is that if your pages are being modified often the visitors will not see the updates until the cache is cleared. That is why I set browser caching to 1 day. And you can see the improvement as in February 2013 I put the browser caching code in .htaccess file. I did want to try W3 Total cache browser caching as I am trying to learn about browser caching. But you can see the performance difference to my server as the bandwidth has dropped from about 140 - 180 to 118 MB. So clearly less data is being processed and sent out by the server so my CPU usage should drop some more.
Sorry, I am late for church - have to go.
1. I didn't want to sign up for the Akismet API key that is why I am not using Akisment.
4. I might remove Google Analytics Dashboard as I am not really 'using' it, will do some more checking. It has these tiny charts that shows how many visitors I had for each article when I use the WP control panel to view all posts. That was very helpful.
The others, well I have not checked out Jetpack and may need to see how it works for others and a review. As for the 3 caches W3 Total cache, PHP Cache and Widget Cache, as I have put in a lot of work analyzing their performance for speed of page download to the visitors PC, I won't replace them with Jetpack just yet. Most of my articles have 7 to 14 photos 448x336 pixels per article so caching them on the server side did help a lot.
As for 1-click Retweet/Share/Like that was the only plugin, at that time when I was looking, that had a nice row of buttons for the top or bottom of the page. Many have floating buttons that keep irritating me. I only wanted buttons at the bottom of the page so that after a visitor has read the article they could decide if they wanted to 'like' or 'share'.
But that does not explain why on January 11th 2012 when there was a flood in Chicago the CPU usage went to 15%. They had blocked a whole range of IP addresses, not just mine, on and off. The servers could not be accessed most of the day, which means that the CPU's were idling, which means the CPU usage should have dropped to almost ZERO %.
I used to have high CPU usage on another site - different hosting account, but the third party software developers are changing their code to reduce the CPU usage.
Some data:-
Awstats
Day Number of visits Pages Hits Bandwidth
1-Nov-12 978 3,818 7,208 183.80 MB
2-Nov-12 972 3,253 6,493 172.91 MB
3-Nov-12 854 3,170 6,331 167.64 MB
4-Nov-12 964 3,960 7,695 213.11 MB
5-Nov-12 956 3,778 7,777 158.86 MB
6-Nov-12 1,022 5,138 11,288 169.77 MB
7-Nov-12 985 4,849 7,182 140.03 MB
8-Nov-12 947 3,773 6,587 158.01 MB
9-Nov-12 1,038 3,852 6,431 143.28 MB
1-Feb-13 796 3,114 5,209 123.96 MB
2-Feb-13 789 2,537 4,421 117.15 MB
CPU Data
Day CPU Time (s) Execution Time (s) CPU Usage Average memory Processes
1 1,168.29 40,964.88 3.38% 4.58 MB 2359
2 1,075.33 37,470.76 3.11% 4.60 MB 2191
3 971.84 35,145.59 2.81% 4.60 MB 1986
4 1,084.36 39,425.82 3.14% 4.60 MB 2247
5 1,341.44 44,232.04 3.88% 4.63 MB 2616
6 693.72 24,212.21 2.01% 4.61 MB 1443
7 1,874.62 47,205.26 5.42% 4.61 MB 2688
8 1,239.65 40,259.80 3.59% 4.60 MB 2301
9 1,208.61 39,445.58 3.50% 4.60 MB 2297
1 2,832.20 37,159.93 8.20% 4.63 MB 2210
2 2,211.90 26,269.64 6.40% 4.59 MB 1526
Analysis of above data:-
Day Test Execution Test CPU Test Processes Processes/CPU sec
1 2.02
2 37,692.54 1074.965059 38,047.50 2.04
3 33,856.22 971.600418 33,964.82 2.04
4 39,273.01 1085.970676 39,764.42 2.07
5 48,717.26 1339.909809 45,900.29 1.95
6 22,914.02 694.9212371 24,398.64 2.08
7 65,288.65 1870.62806 45,102.16 1.43
8 31,266.95 1241.676347 40,408.97 1.86
9 39,250.50 1208.572423 40,189.81 1.90
1 92,415.36 2831.600571 37,951.56 0.78
2 29,002.87 2210.497561 25,658.85 0.69
Test execution is calculating how many seconds for the day based upon previous day execution time and CPU % and todays CPU %. The figures are way off. This means that Execution time is not related to CPU usage.
Test CPU shows projecting todays CPU time (s) based upon yesterdays CPU seconds and %. The projections are very close ie there is a correlation.
Test Processes is projecting todays Execution time based on yesterdays execution time and number of processes. The figures are very close which means that execution time is related to the number of processes running.
Porcesses/CPU second is showing how many processes run per CPU second used. This clearly shows that in November 2012 the server was able to run 2 processes per CPU second but by February 2013 the figure has dropped to 0.78 processes per CPU second. The only the only thing I have done to WORDPRESS was to upgrade it over the months since March 2012. All other plugins had been installed before August 2012. In February or end Jan I had upgraded WP to ver 3.5.1 and SEOPressor to v5 and I implemented browser caching in my .htaccess file
## EXPIRES CACHING ##
<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType image/jpg "access 1 day"
ExpiresByType image/jpeg "access 1 day"
ExpiresByType image/gif "access 1 day"
ExpiresByType image/png "access 1 day"
ExpiresByType text/css "access 1 day"
ExpiresByType application/pdf "access 1 days"
ExpiresByType text/x-javascript "access 1 day"
ExpiresDefault "access 1 day"
</IfModule>
## EXPIRES CACHING ##
Browse caching is very usefull and powerful technique if your images are repeated across all your pages. It saves a lot of back and forth communications between server and client and reduce content download so pages appear almost instantly on the client side. But one drawback of browser caching is that if your pages are being modified often the visitors will not see the updates until the cache is cleared. That is why I set browser caching to 1 day. And you can see the improvement as in February 2013 I put the browser caching code in .htaccess file. I did want to try W3 Total cache browser caching as I am trying to learn about browser caching. But you can see the performance difference to my server as the bandwidth has dropped from about 140 - 180 to 118 MB. So clearly less data is being processed and sent out by the server so my CPU usage should drop some more.
Sorry, I am late for church - have to go.
Comment