• Hi,

    If a blog grows too big… will things load very slowly when people arive at the blog. By big… I mean many many posts in the database.

    kindly,
    ez

Viewing 15 replies - 1 through 15 (of 18 total)
  • Moderator James Huff

    (@macmanx)

    If a blog grows too big… will things load very slowly when people arive at the blog.

    Only if, by some odd reason, you have chosen to show all posts on the index page of your blog.

    In case anyone was wondering, the current max number of posts you can have on a webserver with a 32-bit processor, its:

    340282366920938463463374607431768211456

    Damn, I’d better slow down my daily blogging before I hit that threshold…

    But seriously, that is a concern, especially with load time. Big reason I chose WP over MT is the dynamic page creation, eliminating the load/rebuilds found in MT blogs.

    Some plugins with complex unoptimized queries may cause slow down.

    masquerade: I thought that “post_ID” is currently defined in the database as “bigint(20) unsigned” and it’s range was from 0 to 18446744073709551615. How did you calculate 340282366920938463463374607431768211456?

    340282366920938463463374607431768211456 would just be the physical limit based on the processor’s type handling. If the WP code limits it to 20 bits (as opposed to 32 bits), then 18446744073709551615 *is* the maximum number of posts in a single WordPress blog.

    mmm, I forgot that it was set as bigint(20), I was just remembering that is an unsigned integer, which can be up to the max integer value in C, which is 2^128 iirc.

    “then 18446744073709551615 *is* the maximum number of posts in a single WordPress blog”

    Man, that’s just not enough!

    That might be a truer statement than you know. If you’re currently young (say early twenties or less), there’s a fair chance that by the time you reach 60, medical technology will have extended lifetimes by up to 100%. By the time you reach 100 (and still hale and hearty), that will be extended by another 100 years. Finally, when you’re around 160 or so, computer technology will have caught up and you’ll have the option of copying yourself to an electronic form – just in case the age-reduction treatments fail ?? And if they do fail and you wake up dead instead of 25, just wait another 100 years for them to be able to grow you a stub body cloned from your original.

    So if you think about it, 18446744073709551615 posts becomes more possible with each passing year.

    I think I’d be smarter to worry about things closer to likelyhood, like that UNIX era thing biting me in the butt…

    RustIndy: Good one. Do you reckon WordPress might be obsolete by then?

    I think there’ll always be an upgrade path. Besides, by the time you make it to post number 18446744073709551616, that won’t be the limit anymore ??

    Unless, of course, you’re running your galactinet server on an antique computer ??

    Don’t forget the beauty of the neural interface plugin. Speeds up time to post immeasurably.

    Moderator James Huff

    (@macmanx)

    then 18446744073709551615 *is* the maximum number of posts in a single WordPress blog.

    Will WordPress v1.6 provide support for 190000000000000000+ posts?

    Popstat or anyone: if your’e really worried about the load time, use the plugin called staticize or a similar plugin that will cache the template and pages so the load is easier on the server.

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘Can WordPress have too many posts?’ is closed to new replies.