4 ms·
I was just looking into optimising a large web application. I told the customer that using a caching layer such as a CDN would help paper over the worst of the
by jiggawatts 6y ago
I was just looking into optimising a large web application.
I told the customer that using a caching layer such as a CDN would help paper over the worst of the inefficiencies in their application and the network stack.
That was true! The download times halved.
However, benchmarks with F12 developer tools showed that while downloads reduced from 200ms to 100ms, the overall load times were still seconds, of which about 50% was actual CPU time.
(This is typical of large, complex sites built by non-experts or organisations where performance is not a primary concern.)
Web sites like these perform very noticeably better if you have more CPU cores or faster CPU cores.
Essentially, CDNs are easy to deploy and 5G provides nearly gigabit download speeds, so the bottleneck has shifted back to the CPU for a lot of the web.
- jacobolus 6y agoThere is no speed of computer which cannot be overwhelmed by badly written code. I guess your point is that sloppy web developers / web companies make poorly performing code and shift the burden of handling it out to visitors’ machines, so those machines have to keep improving to not be left behind? That might be true, but is pretty depressing.
- ghettoimp 6y agoI think "fast, cheap, good, pick 2" applies. Obviously the current bloated, ad-laden state of the web is pretty horrible and indefensible. But if we can keep making compute faster, it should ultimately save programmer time, which can be used to either get cheaper or better programs.
- jiggawatts 6y agoConversely: There is no speed of computer which cannot be utilised to reduce developer effort. Faster computers enable easier programming strategies, which improve net productivity. People are expensive, so giving them better "power tools" improves efficiency. We don't complain that coal miners just need to shovel more efficiently. We give them enormous trucks and hydraulic mining shovels.
- deleted 6y ago[deleted]
- Godel_unicode 6y agoSounds like the argument here is "buy an iPad pro so frontend developers don't need to learn optimization"...?
- mucle6 6y agoBuy an iPad pro because time and time again we have seen that optimizing is not a priority for the majority of business. I think the cynicism here is that if only these frontend developers would just learn to optimize we would all finally be better off. I think there are two factors that push against this though. First, if you learn to optimize then you can charge more for your labor, and you will likely get a job somewhere else. Second, companies exist for profit, and optimizing is not often the most profitable next step.
- izacus 6y agoWhich just means that your 1200$ iPad Pro will be slow in a year because the treadmill will continue.
- saagarjha 6y agoI have an iPad using a four-year-old chip that's perfectly snappy. If this drift exists on iOS (it probably does) it is generally less pronounced compared to the life of the device.
- phkahler 6y ago>> Second, companies exist for profit, and optimizing is not often the most profitable next step. That's true and reasonable. And after this 5nm node, TSMC has 3nm and IIRC 2nm. We are at the point where throwing more hardware at slow software is becoming a non solution. The good news is that in many cases there is a LOT of performance on the table on the software side.
- dodobirdlord 6y agoThe node size numbers have been made up for decades. Even if process shrinks bottom out two or three node shrinks from now there will still be improvements in process, materials, thermals, and packaging to allow things like greater z-axis stacking. And there's a ton of room for targeted improvement in things like vector instructions. That's not to say that there isn't an enormous amount of improvement available in software. Projects like simdjson prove that there's a 2x or more improvement available for many high-performance use cases by migrating to vector instructions. https://github.com/simdjson/simdjson https://github.com/simdjson/simdjson