space consumption?

Just take your average post character count, multiply it by however many posts, that’s a round under-estimate of the number of bytes total. Depending on post length, even figuring a 20% overhead is probably high (at least from my point of view). So for roundness sake, lets say 1K characters per post, every other day, for a year, is approx 180K. Throw in some overhead and you’re still under a meg. ?? My referer log is an order of magnitude larger than my blog, and my posts are press releases or articles, both very large content — yet my posts table is under 300K still.
-d
https://www.chait.net

I did a quick check of how much space my MySQL database for WP is using. I’ve been posting since March, on average once every other day (maybe give a day) and the size is only 146.9 KB. The actual news “content” only accounts for 68 KB.
In a nutshell, not much, unless you post text heavily marked-up with HTML.

more than an years worth of posts less than a meg of compressed sql data…

I write a *lot* – junk mainly ??
My stats say that I have made 328 posts consisting of 43,000 words and 322 comments consisting of 8,600 words.
My .sql ‘one click’ backup file is 814K.

MT would be ashamed… ??

I had 2 MT blogs off the same install and it was taking up around 40MB. Now I have 4 WP blogs off of 4 different installs and now it’s less than 11MB. In this aspect (among many others) WP blows MT away.

static htmls :O)
how can it possibly compete!

Here’s a word I don’t miss…..Rebuilding

Wow !
Profanity in the forum !!!!
??

wow, ok then, didn’t realize it took THAT small of a footprint.. i was expecting a few megs maybe… hehe.. thanks

I imported 3,500+ entries and 5,000+ comments. Using MT, my database size was 54.3 meg and took up 180 meg of disk space. With WP, my database is all of 8.2 meg and I?m using only 52.99 meg of disk space.
In other words, it’s a considerable savings.

that should be put somewhere on the frontpage with the other features of WP ??

Aw, you’re just saying that because I’m a fellow Opera fan. ??

There is a new space hog in WP 2.0 somewhere. If you look at your wp_options table, you’ll see some entries that begin with rss_ and that have a bunch of numbers after them. These are serialized arrays that contain other people’s blog content.

I just reduced the size of my options table from 265,572 bytes to 17,748 bytes by deleting these entries.

I have three blogs in one database – by cleaning up all three options tables, I reduced the size of my backup file from 274KB to 158KB.

What I don’t know is what part of WP is adding these monster rss_ entries to the options table or how to get it to stop doing that.

Can anyone help?

P.S. Don’t try this at home – I don’t recommend deleting the rss_ entries without a backup.

The dashboard is doing that.

If you don’t go to that page, nothing should enter the db.
Or you can create an index.php which strips the whole lot out – which leaves you with nothing so you’d not visit it …