3 ms·

This is not sarcasm. I've encountered news sites that do over 15,000 requests and load chains and waterfalls of tracking, invasive garbage, stuff that is illega

• barumi 6y ago
  > I've encountered news sites that do over 15,000 requests I'm not sure if you're joking or not, but in the event you were being serious I should point out that the performance impact of doing a lot of requests is not due to the CPU but time wasted while waiting for the request to arrive. You'd be hard pressed to find a hardware-based strategy for the client-side that would make servers send their replies faster. And while the client waits for a reply, their CPU just idles.
  • ev1 6y ago
    I'm not joking, but the real problem here is all the hot steaming dogshite that they choose to load, not really the number of requests, IMO. Many of those requests are also running GPU code to fingerprint clients. Canvas and WebGL. To "prevent clearing cookies to bypass paywall" fraud and ban scrapers.
    • barumi 6y ago
      > I'm not joking, but the real problem here is all the hot steaming dogshite that they choose to load, not really the number of requests, IMO. Neither making requests not transferring data around are CPU-bound activities. > Many of those requests are also running GPU code to fingerprint clients. Canvas and WebGL. To "prevent clearing cookies to bypass paywall" fraud and ban scrapers. Even taking these statements at face value, considering that javascript is single-threaded by default it still sounds like a perceptual performance problem (not real performance problem) resulting from a poor software architecture. Expensive tasks are expected to be offloaded out of the main thread to avoid getting it blocked.