24-core CPU and I can’t move my mouse

Post by deelowe » Mon, Jul 10, 2017, 2:53 PM UTC

ShinTakuya wrote: post #60

blunte wrote: post #37

This is great work. I hope MS can improve Windows 10 by fixing this. I just added a new Win10 laptop with much better specs than my 3 year old rMBP, and I'm shocked by how much apparently random latency I experience with the UI in Windows 10 compared to the Mac. That's not to mention the issues of sloppier track pad (which constantly detects my left hand while I type) or the ungodly slow unzip (via 7z). If only Apple…

I mean the trackpad issue is generally down to the manufacturer and the drivers they provide, but I take your point otherwise. A pro tip with 7z is to use the two pane interface to extract and not dragging files to Explorer. The latter option extracts the files to a temp directory before copying them whereas the former extracts directly to the destination. The Windows file systems are pretty cruddy in general though…

Post by inglor » Mon, Jul 10, 2017, 2:58 PM UTC

mmarks wrote: post #262

titzer wrote: post #45

Full disclosure: I work for Google on Chrome. A Chrome build is truly a computational load to be reckoned with. Without the distributed build, a from-scratch build of Chrome will take at least 30 minutes on a Macbook Pro--maybe an hour(!). TBH I don't remember toughing out a full build without resorting to goma. Even on a hefty workstation, a full build is a go-for-lunch kind of interruption. It will absolutely own a…

Not to take away from your point, but in my experience the vast majority of C++ build pipelines even at major companies can still be improved. Few people enjoy 'improving the build', it often touches everything, and requires discipline to keep it working. Most of the projects I've worked on have been larger than Chrome, I've seen the compile time for BioShock Infinite go from 2 hours down to 15 minutes with serious w…

Post by vivekseth » Mon, Jul 10, 2017, 3:08 PM UTC

mac01021 wrote: post #258

faragon wrote: post #232

Why the OS don't prioritize UI threads on one or two cores?

How does it know which threads are UI threads?

Post by cheez » Mon, Jul 10, 2017, 3:11 PM UTC

lallysingh wrote: post #250

cheez wrote: post #178

Earlier quoted context omitted.

I use this liberally. Generally, it is a runtime performance issue only on repeated allocations for which you can optimize if needed. Once-only allocations can be ignored when using compiler firewalls.

And the second cache miss: 1 for the cache miss, 1 for the actual object.

Post by mmarks » Mon, Jul 10, 2017, 3:16 PM UTC

inglor wrote: post #303

mmarks wrote: post #262

Earlier quoted context omitted.

Not to take away from your point, but in my experience the vast majority of C++ build pipelines even at major companies can still be improved. Few people enjoy 'improving the build', it often touches everything, and requires discipline to keep it working. Most of the projects I've worked on have been larger than Chrome, I've seen the compile time for BioShock Infinite go from 2 hours down to 15 minutes with serious w…

Just as a data point - Chrome has more code than the linux kernel - Would you say BioShock Infinite seriously has a larger code base than Chrome? I think a lot of people don't estimate correctly just how huge Chrome is.