WordPress.org

Ready to get started?Download WordPress

Forums

space consumption? (17 posts)

  1. lnguyen
    Member
    Posted 10 years ago #

    How big to wordpress blogs tend to get? Assuming a person posts say every other day on average.
    Anyone have any estimates on this?

  2. davidchait
    Member
    Posted 10 years ago #

    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
    http://www.chait.net

  3. Anonymous
    Unregistered
    Posted 10 years ago #

    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.

  4. OperaManiac
    Member
    Posted 10 years ago #

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

  5. Mark (podz)
    Support Maven
    Posted 10 years ago #

    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.

  6. OperaManiac
    Member
    Posted 10 years ago #

    MT would be ashamed... :P

  7. trench
    Member
    Posted 10 years ago #

    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.

  8. OperaManiac
    Member
    Posted 10 years ago #

    static htmls :O)
    how can it possibly compete!

  9. trench
    Member
    Posted 10 years ago #

    Here's a word I don't miss.....Rebuilding

  10. Mark (podz)
    Support Maven
    Posted 10 years ago #

    Wow !
    Profanity in the forum !!!!
    :)

  11. lnguyen
    Member
    Posted 10 years ago #

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

  12. Anonymous
    Unregistered
    Posted 10 years ago #

    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.

  13. OperaManiac
    Member
    Posted 10 years ago #

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

  14. Anonymous
    Unregistered
    Posted 10 years ago #

    Aw, you're just saying that because I'm a fellow Opera fan. ;)

  15. twnyny
    Member
    Posted 8 years ago #

    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.

  16. Mark (podz)
    Support Maven
    Posted 8 years ago #

    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 ...

  17. twnyny
    Member
    Posted 8 years ago #

    Thanks for the quick response.

    Since you go to the Dashboard automatically when you login, it's hard to avoid it entirely. But based on your tip, I figured out another solution.

    Patching WordPress files directly is stupid for lots of reasons, but in the wp-includes folder there's a file called rss-functions.php.

    Changing line 671 from:
    update_option($cache_option, $rss);
    to:
    update_option($cache_option, "");

    is another way to prevent these huge entries from being re-stored in the database once you get rid of them.

Topic Closed

This topic has been closed to new replies.

About this Topic