Displaying 1 To 17 Of 17 Comments The Impact Plugins Have On WordPress Loading Times Hey I have an idea – bbPress could just use the backend and run standalone so it’s far faster and lighter than WordPress ever was. Oh wait, we already had that – it’s called bbPress 0.9 and it was fantastic. The tests that are published on that site are kinda useless – no WordPress install operates in a single-page-at-a-time-to-a-single-user – you’d have to test it under load from multiple connections – the impact of one plugin may be a fraction of second but with a dozen connections to the server, some things scale very poorly. You also need to test first page load and then second page load to see if the plugin behaves differently and for logged in and non-logged in users. » Posted By _ck_ On January 11, 2012 @ 12:13 PM bbPress 2.0 Stable Now Available Remember it’s not actually “bbPress”, it’s an entirely different program, actually a very large plugin that runs under WordPress. They kept the name and mashed up the support website with both programs for some reason that cannot be comprehended, and will keep people confused for a few years to come. I cannot stress this enough – if you are crazy enough to abandon the standalone version, be sure to backup EVERYTHING before you change to this wordpress plugin. Not just the database but also all the core and plugins etc. – you will definitely regret not doing so afterwards. None of my plugins will work with the bbpress “2.0″ version (and never will for what it’s worth). Also if you understand technical issues, imagine a single database table that holds not just every wordpress post but every topic and post from the forum side and the technical issues this causes with mysql locking tables for certain operations (writes, etc.) Large sites should take heed at that core concept. So in a nutshell: bbPress 0.7-0.9 standalone – standalone, super-fast and fixes some important legacy core problem that wordpress had as Matt gets a chance at a “do-over” bbPress 1.0-1.1 standalone – Matt changes his mind on a whim and decides to have them rip out the WordPress core to make backPress which will then power bbPress by ripping out the core functions in bbPress – but it adds an extra layer of “communications” between the two so bbPress 1.x is 50% slower than 0.9 (Sam Bauers leaves Automattic/bbPress at this point, so bbPress is in trouble) Then Matt changes his mind again on a whim and decides WordPress core will never change and never be standalone so backPress is essentially dead in the water despite all the effort put into it, and converting bbPress to use it bbPress 2.0 – a WordPress plugin written from scratch but keeping the same name as the standalone version, essentially so buddyPress can have forums without having to use the standalone version, regardless of the massive performance hit » Posted By _ck_ On September 23, 2011 @ 11:40 AM BuddyPress And bbPress Are Getting A Divorce Note that “bbPress 1.2″ is an entirely different program than all previous versions of bbPress. It will contain very little code from bbPress 1.1 They simply hijacked the name because, well because Matt can just say so on a whim and abandon the 10k+ existing users. I’ve asked repeatedly for a name change or at least calling it 2.0 instead of 1.2 because of the massive differences and how no existing themes/plugins will be compatible, but it doesn’t look like they are even going to honor that. So when you say they are “getting a divorce” keep in mind it’s not even the same entity, as confusing as that is. » Posted By _ck_ On August 18, 2010 @ 8:00 AM Plugin And Theme Devs Have Reason To Celebrate Note that 11 percent of ten million is over a million users below 5.2. So they are going to hassle a non-trivial number of users (in that not keeping up with WP updates is very hazardous to your site’s health). It’s VERY easy to code around MySQL 4/ PHP 4.4 limits, in fact they are going to have to go out of their way to force WP3 not to support it. But to be fair, a year of warning is plenty of notice. I have a bigger problem with the drop of support for MySQL 4.1 because on small/medium sized MyISAM tables it is measurably faster than MySQL 5.x » Posted By _ck_ On July 27, 2010 @ 2:39 PM Akismet Looking For New Testimonials Akismet has a big problem but it’s not catching spam. The problem is the constant false positives. This keeps moderators very busy, it’s very annoying and completely confuses new users who sometimes get “spammed” without understanding what has happened (and then admin sometimes miss the user’s post for days). Before asking for testimonials they should work on reducing that problem. » Posted By _ck_ On July 23, 2010 @ 2:49 PM WordPress Support Forum And Themes You should NEVER allow the use of EVAL in any of your plugins or themes. Not only is it a huge security risk, it’s also a big performance hit. » Posted By _ck_ On June 26, 2010 @ 2:19 AM MattNote From WordCamp San Francisco Wow, I see bbpress.org 2.0 was just made live today? Sam did an amazing job on that, very happy to see it in use. Thanks for making that happen Matt. ps. I am getting a blank page sometimes, especially when going into plugins section… » Posted By _ck_ On May 3, 2010 @ 11:00 PM Let’s be clear: bbPress was a perfectly fine product with 0.9 – it is a fairly efficient forum framework. Matt can only blame himself for changing course and steering it in the wrong direction with 1.0 – massively bloating the code by having it converted to use “backPress”. But then backPress was never folded back into WordPress so the whole extreme effort became pointless. bbPress was left bloated and broke many existing plugins, resetting the whole community’s progress. bbPress will never work as designed as a plugin for WordPress because the WordPress plugin structure has become far too outdated and inefficient. You can’t have a competitive forum product with over a megabyte of code loading and several dozen queries for every page render. This is why existing forum plugins for WordPress are not popular. But bbPress 0.9 by itself works wonderfully as a standalone or in pair with WordPress. Sam Bauers worked damn hard to make Matt’s bbPress 1.0 directive come true and it’s practically a crime that his work on bbPress.org 2.0 will never see the light of day because it was also a very fine effort that could have really grown and solidified the community. Automattic should not be a “one-hit wonder” with WordPress – bbPress 0.9 should have been finished as originally designed. » Posted By _ck_ On May 1, 2010 @ 6:13 PM Raw Look At The Trackback Attack donnacha, I assure you, many automattic servers are still running LiteSpeed and it’s easy to prove based on certain responses to certain queries. There is no 15-day timeout on the free version of Litespeed, only the commercial version. The free version has a limit of 5 httpd.conf accounts and 100 simultaneous connections (1500 can be queued). It’s definitely not for everyone but something to try when a site outgrows apache. If starting from scratch I would definitely use nginx, but if you need a drop in apache replacement that can be done in less than an hour, use litespeed. It’s literally doubles the capacity of any server that was using apache. I am not a fan of the commercial price tag and I hope they feel the pressure from open source alternatives over time to reduce that. I do agree with you that shared hosting is a bad idea for any larger site. The wrong VPS environment can be just as bad because it’s a complete lie you are isolated from neighbors on the node. But not everyone can afford dedicated so the right VPS is a good solution. » Posted By _ck_ On March 29, 2010 @ 1:03 AM Always delete xmlrpc.php immediately from virtually all WP installs. If you are on a dedicated or VPS (and you should be) I highly recommend the (free) configserver firewall http://configserver.com/cp/csf.html – it’s not just for cpanel anymore and it’s extremely good about blocking too many connections. Last but not least when you can’t solve a ddos, replace apache with something like litespeed which is a drop in replacement (uses httpd.conf and .htaccess files directly unlike nginx). There is a free version and it can weather a ddos when apache would be long dead. Even automattic uses litespeed to this very day. » Posted By _ck_ On March 25, 2010 @ 11:52 AM CodePoet.com – New Home For WordPress Consultants If the internet is international and doesn’t have boundaries, why restrict by region? And why is WordPress the only Automattic product handled? » Posted By _ck_ On September 17, 2009 @ 12:26 AM WordPress Dev Chat For 7-30-09 @Dougal, You’re right, I forgot that WordPress phones home with everyone’s server information (unless you know how to unhook the action, there is no opt-out or opt-in or warning about privacy). So they do indeed know 99% of everyone’s PHP info, their server version and IP, what plugins they use and other info. My PHP version statistics are not made up and not out of thin air, I really did survey that many sites for bbPress back in April (and will include thousands more in October). However I did glance at them wrong in my rush to post and did not add up the different 5.x versions properly, so the PHP 4 use is closer to 25% than 50%, but most certainly higher than 15%. I’ll post the exact numbers of what I find in October on bbPress.org. The WordPress community is NOT just made up of sophisticated users on dedicated or VPS servers who know what they are doing and how to keep up with PHP. There is a far greater number of average users on shared hosting who do not have control over their PHP (nor want to care about it, they just want to blog). I don’t think PHP 4 should be supported “forever” or past next year. But another year isn’t going to kill WordPress development. There is nothing so wonderful in PHP 5 that can’t be easily emulated in PHP 4. I have no problem with a nag in 2.9 (and 2.9.1 and 2.9.2 and 2.9.3 lol). » Posted By _ck_ On August 4, 2009 @ 12:53 AM Sorry, I should correct my thoughts in that not all WP Devs are gung-ho for 5.3, only a select few. And it’s not 15% of the userbase using PHP 4, I’ve done a survey of 6000+ sites running bbPress and WordPress and the number is closer to 50% » Posted By _ck_ On August 3, 2009 @ 1:48 PM It’s hilarious how WP devs are in a rush to use x.0 products like 5.3.0 Somehow I do hope they force the 50% of people still on PHP 4 to stop using WordPress and search for other programs. It can only help other projects. So: 1. force people to keep upgrading constantly to maintain security no matter how it keeps breaking everything 2. eventually make a version 50% of your base can’t upgrade to because it won’t work on their host, leaving them open to security issues Should end well. ps. Objects are not faster, they make it easy to cache bloated things but they certainly are not faster by any means. All that copying around in memory adds up. Running on 5.3 will give you a 5-15% speed boost over 4.4.9 but it doesn’t magically thin bloated code. » Posted By _ck_ On August 3, 2009 @ 1:44 PM Small Town Rebels Against Blogger It’s a shame WHY she said it got drowned out by egos who were “offended”. » Posted By _ck_ On July 28, 2009 @ 12:22 PM The Crossing Paths Of Drupal And WordPress Somewhat related and less known is this public “showdown” competition entered by each company (WPMU+bbPress vs Drupal vs Joomla) back in March: http://cmsshowdown.com/competition (check out the PDF at the end) » Posted By _ck_ On July 23, 2009 @ 12:58 PM Listener Poll: Do You Think bbPress Will Evolve Into A WordPress Plugin? To understand why bbPress will never be a plugin, you have to understand bbPress history. bbPress was written out of parts of WordPress code by Matt (in just a few days) to replace minibb on WordPress.org. It was released a couple years later as 0.7 under GPL so it could benefit from the free labor of community contributions, just like WordPress. bbPress 0.8 and 0.9 actually corrected several of the “mistakes” in WordPress that have become a burden of legacy and backwards compatibility. But with 0.7-0.8 integration was not a main focus and no attempt was made to make it particularly easy, though it was possible. By 0.9, integration had become quite a bit easier (that is until WP 2.6 then 2.7 then 2.8 kept changing the @$%!@$ cookies and breaking compatibility). Matt then decided to have TalkPress created, which is like a forums version of WordPress VIP – Automattic hosted forums for premium customers. However he wanted an easier to maintain code base between the projects and object based caching like WordPress, so he directed that a subset of WordPress code be created (backPress) and replace the existing code in bbPress. So bbPress 1.0 as it stands now is a rather different creature internally than 0.9 – it maintains most of the 0.9 compatibility thanks to a massive effort by Sam (but still breaks enough to be a pain in the @#$ to plugin developers). However because of the backPress bloat from WordPress, it’s now 50% bigger than the relatively lightweight 0.9 and takes 50% longer to generate most pages due to it’s increased complexity to interface with backPress. Until WordPress itself is changed to also use backPress therefore sharing code during integration, and to the best of my knowledge there is no such intent stated on even the far future timeline, deep integration of bbPress into WordPress requires a massive amount of code to be loaded and executed for every page (nearly 1 MB per instance) and at least 30 queries per page BEFORE plugins do their thing. Such a load would get a user kicked off most shared hosts without caching on a busy site and forums don’t lend themselves to page caching as well as a blog because members typically get non-cached pages. So no, bbPress will never be a plugin for WordPress. ps. all of this is simply my opinion based on observation and experience » Posted By _ck_ On July 22, 2009 @ 4:00 AMComments Posted By _ck_
It’s responsible for several of the security issues with WP over the years, and it also allows unlimited password attempts. You can live without the mostly spam trackbacks for the safety of it being gone.
They’re only on 2.8.3 already in 30 days and possibly not done yet.
Alaska has 250% more rape cases than any other state.
(now just imagine how high the real unreported rate is)
Nothing done by the state to address it, never gets national attention.
«« Back To Stats Page
(but there will be a plugin for WordPress to automatically INSTALL bbPress, which I think is a different animal entirely than what you are asking)