5 ms·

>1. Performance. also please note: if you have 1 image on the page - we have to do 2 requests (1 metadata, 1 download) if you have 50 images on the page - we

• jedberg 4y ago
  > if you have 50 images on the page - we have to do 51 requests only (1 metadata for all images, 50 downloads) But unless you return the same host for 50 objects, I'm going to have to do a bunch of DNS lookups too, right? And a bunch of SSL setups. Hopefully you at least make sure to try and return a single host for all the objects in a request.
  • mranton 4y ago
    >Hopefully you at least make sure to try and return a single host for all the objects in a request. our goal is to saturate the _User's_ network. Now it's hard to say how many Peers we need to meet this requirement. It looks like 2-3 Peers are enough. Also, when you have 50 Peers, you have to do 50 DNS/SSL requests in _parallel_. With current hardware, it's not a big deal.
    • pwinnski 4y ago
      > With current hardware, it's not a big deal. You should make this your marketing slogan. "Try our CDN, with current hardware the gross inefficiencies other CDNs spend a lot of time and effort eliminating are not a big deal."
• chx 4y ago
  > if you have 50 images on the page - we have to do 51 requests only (1 metadata for all images, How do you know the nearest peer has all the images at hand?
  • mranton 4y ago
    to answer this question, I will write another article how we distribute cache among the Peers. Long story short: - we divide web cache in buckets - these buckets have different sizes - we know a list of files in every bucket - we know what buckets every Peer has