Comments on: Plugins To Avoid http://www.bloggingpro.com/archives/2006/12/01/plugins-to-avoid/ News, plugins and themes for blogging applications Fri, 10 Feb 2012 01:07:34 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: aydin-aydin http://www.bloggingpro.com/archives/2006/12/01/plugins-to-avoid/#comment-215237 aydin-aydin Thu, 18 Sep 2008 08:23:33 +0000 http://www.bloggingpro.com/archives/2006/12/01/plugins-to-avoid/#comment-215237 Patent, Marka Patent, Patent Ofisi, Patent Dirsek, Patent Office, Patent Tescil, Patent Burosu, www patent, Patent com, Patent Ofisim, Patent Tescili, marka patent tescil, patent alma, turk patent, tasarim tescili, tescil belgesi, tasarim tescil, marka tescil, marka tescil belgesi, marka tescili Patent, Marka Patent, Patent Ofisi, Patent Dirsek, Patent Office, Patent Tescil, Patent Burosu, www patent, Patent com, Patent Ofisim, Patent Tescili, marka patent tescil, patent alma, turk patent, tasarim tescili, tescil belgesi, tasarim tescil, marka tescil, marka tescil belgesi, marka tescili

]]> By: sohbet http://www.bloggingpro.com/archives/2006/12/01/plugins-to-avoid/#comment-214380 sohbet Wed, 23 Jul 2008 21:52:08 +0000 http://www.bloggingpro.com/archives/2006/12/01/plugins-to-avoid/#comment-214380 And yes, I recall that Gravatar-related plugins were among the Plugins to Avoid we recently wrote about. And yes, I recall that Gravatar-related plugins were among the Plugins to Avoid we recently wrote about.

]]> By: Angsuman Chakraborty http://www.bloggingpro.com/archives/2006/12/01/plugins-to-avoid/#comment-105818 Angsuman Chakraborty Sat, 30 Dec 2006 16:25:28 +0000 http://www.bloggingpro.com/archives/2006/12/01/plugins-to-avoid/#comment-105818 I think he unfairly implicated us for performance of WordPress object cache. Translator plugin Pro uses dual caching to speed up your access time. The first level cache doesn't use the WordPress object cache and will improve your performance even with standard caching disabled. The second level cache uses WordPress Object cache. This allows us to serve your translated pages much much faster. We did extensive testing with the WordPress object cache to identify performance bottlenecks, if any. We couldn't find any inherent problem. It can cause performance penalty only when the memory is low and too many Apache processes are allowed. With caching enabled each Apache process (or Thread), serving a WordPress page request, caches at most 125 php objects (we only contribute one of them) which can increase memory consumption. As a result kswapd (swap manager) comes into play and at high loads it tends to swap too often and ends up consuming most of the CPU cycles itself instead of allowing actual processing. So if you are on a low end machine with low RAM or if you are sharing the machine with lots of other users then you can experience performance issues. However you can easily solve it by either increasing the memory or reducing the maximum number of Apache processes you serve. In our tests I could repeatedly run 50 simultaneous full site crawl on a big website with over 20, 000 pages (copy of my Simple Thoughts blog with translated pages in 14 languages) without delay (using wget in recursive mode) with only 512 MB RAM without breaking a sweat in low end Intel Pentium (1.8 Ghz) running Fedora Core 4. I was using the Translator plugin in cache mode. The pages were not cached when we started. If that is not good performance I don't know what is. I think he unfairly implicated us for performance of WordPress object cache.

Translator plugin Pro uses dual caching to speed up your access time. The first level cache doesn’t use the WordPress object cache and will improve your performance even with standard caching disabled. The second level cache uses WordPress Object cache. This allows us to serve your translated pages much much faster.

We did extensive testing with the WordPress object cache to identify performance bottlenecks, if any. We couldn’t find any inherent problem.
It can cause performance penalty only when the memory is low and too many Apache processes are allowed. With caching enabled each Apache process (or Thread), serving a WordPress page request, caches at most 125 php objects (we only contribute one of them) which can increase memory consumption.
As a result kswapd (swap manager) comes into play and at high loads it tends to swap too often and ends up consuming most of the CPU cycles itself instead of allowing actual processing.
So if you are on a low end machine with low RAM or if you are sharing the machine with lots of other users then you can experience performance issues. However you can easily solve it by either increasing the memory or reducing the maximum number of Apache processes you serve.

In our tests I could repeatedly run 50 simultaneous full site crawl on a big website with over 20, 000 pages (copy of my Simple Thoughts blog with translated pages in 14 languages) without delay (using wget in recursive mode) with only 512 MB RAM without breaking a sweat in low end Intel Pentium (1.8 Ghz) running Fedora Core 4. I was using the Translator plugin in cache mode. The pages were not cached when we started. If that is not good performance I don’t know what is.

]]> By:   Downtime at Gravatar. Should a New System be in Place? by Blogging Pro http://www.bloggingpro.com/archives/2006/12/01/plugins-to-avoid/#comment-99462   Downtime at Gravatar. Should a New System be in Place? by Blogging Pro Tue, 05 Dec 2006 16:53:06 +0000 http://www.bloggingpro.com/archives/2006/12/01/plugins-to-avoid/#comment-99462 [...] And yes, I recall that Gravatar-related plugins were among the Plugins to Avoid we recently wrote about. [...] [...] And yes, I recall that Gravatar-related plugins were among the Plugins to Avoid we recently wrote about. [...]

]]>