It's Freaky! . . . It's a whole new way of doing things!. . . .Kinda like. . . . .

Actually posting takes up no bandwidth at all. If you figure the largest size of someone's post would probably be 10-20k the only bottleneck would probably be with the sender (who would have the slower pipe) not the recipient, which in this case would be the bladeforums server. Now storage space is a whole different matter if you'd like to use that as a case. While the posts themselves are rather small you'd have to multiply them exponentially considering the number of users. In addition to the post repository you would have to account for the database entries, oh and of course growth for the search index. Most database search indexes run at app. 40-50% of the actual data repository size.

I could see how this might be a "waste" when looking at storage and database performance....but I guess it doesn't matter since the original question was for bandwidth.......
 
Originally posted by Dark Nemesis
Actually posting takes up no bandwidth at all. If you figure the largest size of someone's post would probably be 10-20k the only bottleneck would probably be with the sender (who would have the slower pipe) not the recipient, which in this case would be the bladeforums server. Now storage space is a whole different matter if you'd like to use that as a case. While the posts themselves are rather small you'd have to multiply them exponentially considering the number of users. In addition to the post repository you would have to account for the database entries, oh and of course growth for the search index. Most database search indexes run at app. 40-50% of the actual data repository size.

I could see how this might be a "waste" when looking at storage and database performance....but I guess it doesn't matter since the original question was for bandwidth.......
??:confused: you been smoking glue:confused: ??
 
So.... s-s-s-s-spit it out man. What about the Outlaw?

Are you trying to say we all get a free Fusion NO or what?!
 
Back
Top