4 ms·
Almost every time I install or update something from mac ports, it's ending up compiling, binaries are very rarely cached. I doubt my setup is unusual (the late
by sklogic 12y ago
Almost every time I install or update something from mac ports, it's ending up compiling, binaries are very rarely cached. I doubt my setup is unusual (the latest OS X and the latest XCode).
And I suspect that, for example, JS engines in the browsers are going to be more and more parallel. And that kind of compilation is something that every user does on a daily basis. More cores => smoother web browsing experience. Not that I approve this whole thing that's going on with the JS craze, but it's the fact everyone have to cope with, unfortunately.
- deleted 12y ago[deleted]
- dagw 12y agoMore cores => smoother web browsing experience. When going from 1->4 cores, agreed. When going from 4->16->64 cores I'm not convinced. Especially if those 64 cores are slower and have less cache.
- sklogic 12y agoMy point is that because of stagnation of ILP and cache size, the number of cores will increase anyway, so we'd have to find a way to utilise this resource anyway. Of course, trading single core performance for the number of cores is pointless in most of the desktop use cases.