5 ms·
That's pretty much how MovableType used to work. Fun fact: it was terrible. Most bloggers I know hated it. Wordpress is a bucket of poop too, but it has the q
by jacques_chester 15y ago
That's pretty much how MovableType used to work.
Fun fact: it was terrible. Most bloggers I know hated it.
Wordpress is a bucket of poop too, but it has the quality that when you press 'publish', the site is updated in seconds, not minutes.
(I believe MT has changed since then).
- flyosity 15y agoI've been using MT since 2003 and never thought it was terrible. Publishing times (full-site publishing) was always slow but publishing an entry only took a few seconds. The new Melody project forked MT and updated the UI, it looks great now.
- byoung2 15y agoI used MovableType when rebuilding steves-digicams.com (not by choice), and it really slowed to a crawl when we did a full publish (30,000+ articles). Luckily we only had to do that a few times when setting up the site. I don't see the advantage of static files being worth the hassle of publishing when you can achieve the same or better results using a caching proxy like Varnish. We used Varnish in front of Apache on ultimatecoupons.com (all dynamic, built in the Symfony PHP framework), and once cached, pages load in 15ms (first byte in browser).
- g-garron 15y agohttp://daringfireball.net/ http://daringfireball.net/ uses Movable Type and gets a lot of visits, and I'm sure it can handle a lot more. Yes, static content is the key.
- pwaring 15y agoIt's how Greymatter and a few other systems used to work as well. The main problem was determining which pages should be updated, which usually resulted in the entire blog being rebuilt. This took several minutes if you had a few years of archives, and if anything went wrong part-way through the process you had to start it all again.
- jacques_chester 15y agoI've ruminated in the past about a better blogging system based on updating on-disk caches based on POST and not GET. I think everybody who watches Wordpress trip over and burst into flames when you so much as breathe on it has. The main problem to solve is inter-page dependency. The rest is not that hard /famouswords.
- pwaring 15y agoYou can get too carried away with scalability though. I run half a dozen WordPress blogs, plus some static sites and email for multiple domains (with AV and spam filtering) within 500MB of RAM. I don't need to implement any caching because I already have sufficient resources.
- mkr-hn 15y agoGet this: http://wordpress.org/extend/plugins/w3-total-cache/ http://wordpress.org/extend/plugins/w3-total-cache/ It's called a caching plugin, but it also compresses and minifies stuff. Any site can benefit from loading faster. You can turn it on and let it go. It has sane defaults.
- rawsyntax 15y agoThanks for the info, after hearing people praise wordpress as the holy grail of blogging, I found it to be very very slow. Hopefully this plugin will help
- easp 15y agoI found that a major contributor to page generation times on Wordpress is the time taken to load and parse all the PHP files. I installed a PHP opcode cache (APC) as I recall, and it made a huge difference, because the parsed representation of all the Wordpress code is cached in memory (or disk). I'd do that before installing any Wordpress caching plugins, though total cache has other nice features, like minification. Plus it has three different levels of caching. You can cache entire generated pages, and/or objects and/or DB results.
- burgerbrain 15y ago"the site is updated in seconds, not minutes." That is an implementation issue. That problem is in no way inherent to static content.
- voltagex 15y agoThe problem with saying "Wordpress is poop" - as a developer, that problem report has no info I can actually use to fix anything.