Stories
Slash Boxes
Comments

SoylentNews is people

Lowering Bandwidth Costs for Slash-based Sites

posted by janrinok on Wednesday March 12 2014, @11:33PM   Printer-friendly
from the I-was-doing-OK-until-it-mentioned-perl dept.

xyzzyyzzyx writes:

"Avantslash is touting a user hosted perl script that, if paired with any web browser with JavaScript, promises to shave crucial bytes off of the standard Slash-based experience, one of which is our very own SoylentNews. Audiences include those with very limited bandwidth, such as those in developing countries with only 2G mobile access or dialup."

 
This discussion has been archived. No new comments can be posted.
Lowering Bandwidth Costs for Slash-based Sites | Log In/Create an Account | Top | 58 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 1) by VanessaE on Thursday March 13 2014, @05:54AM

    by VanessaE (3396) <vanessa.e.dannenberg@gmail.com> on Thursday March 13 2014, @05:54AM (#15721) Journal

    Simple. If you only manage to shave off 1kB per page, you're already looking at 5GB/mo less bandwidth for the 5M views/month this site gets now. If Soylent can manage to get to Slashdot-levels of traffic (15M views/mo) and the savings is more substantial, say 25 kB per page, then you're talking about 375 GB/mo in saved bandwidth.

    Consider for a moment how much time it would take to send 375 GB, and what else one could do with that bandwidth if it's just being wasted now.

    Multiply that again by however much traffic all of the other Slashcode-using sites are getting, combined.

    Also consider that not every geek has a particularly fat pipe. A few seconds saved here and there loading pages adds up.

  • (Score: 1) by Titanium on Thursday March 13 2014, @09:38AM

    by Titanium (1840) on Thursday March 13 2014, @09:38AM (#15772)

    (375 gigabytes) / (10 (gigabits per second)) =
    5 minutes

    I fail to see your point, and I did not even multiply by the number of nodes serving up the page.