4 ms·
Yes, we do. But I doubt anyone is using them for production workloads. Development workloads don't continuously push cpu to 100% or even 70% for large periods o
by quantummkv 9y ago
Yes, we do. But I doubt anyone is using them for production workloads. Development workloads don't continuously push cpu to 100% or even 70% for large periods of time. Development workloads don't make 1000 req/sec on postgres. No one has 10 vm's running at a time on a desktop.
These perf issues will only affect the server and cloud providers or some edge cases on the desktop. Everyone else can just apply the patches and go to work.
- discreteevent 9y agoYou are probably right although C++ compilation can use a fair bit of processor, especially with parallel compilation (e.g. Qt jom). Not sure how frequent system calls are though.
- kasabali 9y agoC/C++ compilations typically read and write a zillion different tiny files and even if they happen totally in memory buffer they'll still do a hell a lot of system calls.
- stevefan1999 9y agoI think parallel compilation is going to be hit the most. On my VS2017 with the latest MSVC and C++17, and a moderate C++ project (very few units, only about 100 files and so many constexpr and TMP) with multi core compilation enabled, plus a E5-2660, I have a record of 10% penalty(originally a minute) in build time after clean-and-rebuild. Haven’t tested with IncrediBuild tho, but my paralleled webpack production build seems to offer the same outcome. 30 secs to 36 secs. Both of which is not that really mattered I’d say. I’m using Windows 10 with KB4056892.