Does WordPress slow down your server?

It will kill your server if you use the mod-rewrite option where it adds a redirect to your htaccess file every time you add a page. My htaccess file was 70kb.

what's the purpose of that?

It takes http://domain.com/index.php?/my-big-dick/ and turns it into http://domain.com/my-big-dick/

It looks cool and makes some things easier, but honestly its a resource hog and total waste. I haven't messed with WP enough to know if there's an "easy fix", but I really don't think there is. I have no idea what they were thinking. My blog had about 300 pages and was killing my box. We moved all of the redirects to my Apache configuration as a temporary fix, but I still haven't fixed the problem.

Why would you add that many pages? The blog entries itself don't add additional information to the htaccess file?!

Whoa. I didn't realise it grew thee htaccess with every page. I knew it was there and what it did in terms of redirect but not how it did it. I'll have to keep an eye on all of mine.

whats the purpose of that

I believe permalinks as they are called are more search engine friendly.

that is true. I am just going to up my server to run faster.

ehm... the permalink structure has a fixed size once you set it up in the options menu. are you guys talking about "pages" or posts? Whats the purpose of creating seperate pages?

If you had come nicely to my thread, instead of like an idiot, I would have kindly answered this for you there. But I guess you think it's better to look a little less than brilliant in THIS company than in my thread. Tsk.


2hp

uhm ok... whatever man. just tried to be constructive.

Hmmm hows this Your thread? lol thought I started this thread.
Cant we all just get aloooong?


Joe S.

Constructive is good. I'm all about constructive. Maybe I missed the constructive part of your offering:


But perhaps it's a culture difference.

Now, to answer your question. Here's is what a typical, seasoned .htaccess file looks like inside:

RewriteRule ^comments/(feed|rdf|rss|rss2|atom)/?$ /index.php?&feed=$1&withcomments=1 [QSA,L]
RewriteRule ^comments/page/?([0-9]{1,})/?$ /index.php?&paged=$1 [QSA,L]
RewriteRule ^search/(.+)/feed/(feed|rdf|rss|rss2|atom)/?$ /index.php?s=$1&feed=$2 [QSA,L]
RewriteRule ^search/(.+)/(feed|rdf|rss|rss2|atom)/?$ /index.php?s=$1&feed=$2 [QSA,L]
RewriteRule ^search/(.+)/page/?([0-9]{1,})/?$ /index.php?s=$1&paged=$2 [QSA,L]
RewriteRule ^search/(.+)/?$ /index.php?s=$1 [QSA,L]
RewriteRule ^category/(.+)/feed/(feed|rdf|rss|rss2|atom)/?$ /index.php?category_name=$1&feed=$2 [QSA,L]
RewriteRule ^category/(.+)/(feed|rdf|rss|rss2|atom)/?$ /index.php?category_name=$1&feed=$2 [QSA,L]
RewriteRule ^category/(.+)/page/?([0-9]{1,})/?$ /index.php?category_name=$1&paged=$2 [QSA,L]
RewriteRule ^category/(.+)/?$ /index.php?category_name=$1 [QSA,L]
RewriteRule ^author/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$ /index.php?author_name=$1&feed=$2 [QSA,L]
RewriteRule ^author/([^/]+)/(feed|rdf|rss|rss2|atom)/?$ /index.php?author_name=$1&feed=$2 [QSA,L]
RewriteRule ^author/([^/]+)/page/?([0-9]{1,})/?$ /index.php?author_name=$1&paged=$2 [QSA,L]
RewriteRule ^author/([^/]+)/?$ /index.php?author_name=$1 [QSA,L]

Basically, what is happening is every time you make change that redefines the ways a file or group of files is callable by a browser client, the program establishes those new rules in the htacess and supersedes prior rules. You may have links out there, however that are calling a file by an old name under an old category. WP needs to remember that, and offer the file when called by that name. That's how they get fat.

This is one of the most miraculous thinhs about PHP-based template-generated web sites -- It used to be that files were REAL things, whith a physical location and "physcial" proprties. The concept of the "file" as we knew it is gone. A URI is a unique identifier that calls a certain set of templates, passess them through a particulat CSS and produces X on the browser. This is nothing less than a paradigm shift that very few people are properly appreciating.


2hp

No, sorry -- it's just that he came and shit in my thread and then shows up here with good questions. Seemed ironic to me --


2hp

Are you fuckin retarded? What does your thread have to do with this one anyway? If I give you shit in your thread, you don't need to take it into this fella's thread.

And thanks for, yet again, throwing around with "concepts" and "paradigm shifts". I'm well aware of how htaccess mod_rewrites work. And CSS for that matter, too. Instead of blowing so many fancy words out of your ass, you should get over yourself, royal highness.

Either way, I have several WP blogs running on the same machine, and my htaccess files are much slimmer than 75KB. They are limited to the permalink structure that I once set and never updated since. I never experimented with pages, it may be if you add tons of them to the blog, that it bloats the htaccess. I'll have to try it out.

Actually, re-reading your posts, you seem like you're on some mighty good shrooms. Maybe I should pop some to properly "appreciate" the paradigm shift of a file concept in its meta-physical location... blah blah.

If you fuck with me in my threads, there will be consequences -- period.

I am sure that my response has been appreciated by those readers not intimidated by a little technical speak. I am trying to help, I seem to keep having to remind a certain type here. I can forgive myself coming into this thread to add value (giving an answer I think sheds light). What is your excuse for coming into my well-intentioned, drama-free thread and saying anything negative.

Things be different, now, hoss -- bess choose words careful-like -- -- ya here.



2hp

I just tried it out.

The difference is posting new 'pages' vs new 'posts'
For every new 'page', WP added 4 lines in the htaccess.

I think I will stay away from new 'pages'

Consequences? Can't wait!
I'm still waiting for Amp to ruin my life how he promised three years ago.

GFY is just so full of shit sometimes.

lovely thread again

yea i guess if you leave it as the way youve started your blog, they stay small... i have a blog thats more then 6 motnhs old with about every 2 - 3 days a new post (so all the pages with posts change every 2-3 days) but still its 4kb and stays 4kb, just like all my other (newer) blogs, also around 4kb.

by the way talking about pages - right now im making a new page for a blog and i dont want the date etc. on top of the page, since it will be a 'static' page.
How do i do that? In the theme im using there isnt a seperate 'page.php' file or something.

dont seem to bother mine at all.

Here's my good deed for the day

If you don't have a page.php then maybe it is called something else in your theme.

To make a page.php copy your index.php or whatever file closest resembles the way you want your final page to look. Rename it whatever you want and then stick this at the top of the page.

<?php
/*
Template Name: my_new_page
*/
?>

This should now appear in the drop down list for Page Template on Write > Write Page in Wordpress.

This is when it starts to grow the .htaccess file. When you start to add these sort of pages.

WP is a ridiculous script to use for larger sites. A script using mainly static files could deliver similar functionality and would be much less demanding on the server.

aha ok, thanks im gonna try it

Looks like this issue is now resolved with the WP2.0 release. 36k down to 2k again.

I had to change some of the other stuff in my htaccess to get them to work properly but no longer does the htaccess grow when you add a new page

so, basically if I have 15 wp blogs on the same server on 15 domains & a total of 75+ something pages, I am fucked????

i will have some mainstream stuff for you in a couple days.

not that I know of!

If you're concerned about server load and want to speed it up, almost to a point of static pages, try this plugin http://mnm.uib.es/gallir/wp-cache-2/.

agreed, one of the reasons I'm considering checking out moveabletype, I'm pretty sure someone told me it makes static pages, or bloxsome or any other simple/fast script that poops out static html...

I'd rather keep my mod_rewrite for a forum setup I have that has a set of instructions that is SUPER slim and barely a load at all...