5 ms·
I hate to break it to you, but you’re probably using one of these to read this comment. If you don’t believe me, disable hardware acceleration on your machine
by hedora 6y ago
I hate to break it to you, but you’re probably using one of these to read this comment.
If you don’t believe me, disable hardware acceleration on your machine (force the video card to VESA or framebuffer mode or something), and try to read the news, use web apps, etc. Compare them to native 2D apps, which should still generally work just fine.
In my experience, a modern, headless 24 core xeon with 128Gb of ram and 2x10GBit nics can’t even use jenkins and jira comfortably at the same time.
News sites with JavaScript enabled and no ad blocker are just not usable at all on such a machine.
- Stevvo 6y agoGPU hardware acceleration is not the same as a dedicated accelerator card.
- deleted 6y ago[deleted]
- gruez 6y agoI'm not sure whether this is sarcasm or not. This comment (and most other web pages) work fine without any hardware acceleration enabled. Test software: firefox on windows guest os, with 3d acceleration disabled in virtual machine settings. AFAIK browsers in the early 2000s didn't even have gpu acceleration for rendering.
- ev1 6y agoThis 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 illegal in Europe, from over 250+ domains on a single pageview.
- 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 agoI'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.