7 ms·
Yup. Just waiting on the benchmarks from independent reviewers and to see how XFR in this generation works but I’ll be getting a Ryzen 9 if everything checks ou
by gigatexal 7y ago
Yup. Just waiting on the benchmarks from independent reviewers and to see how XFR in this generation works but I’ll be getting a Ryzen 9 if everything checks out. 24 threads will be amazing for local development (microk8s, and others) when I’m not gaming and save me from having to build a separate box.
- dmix 7y agoDo you work on a desktop machine? At home?
- shmerl 7y agoWhy not? Lot's of FOSS development happens this way.
- dmix 7y agoI didn't say anything bad about it. Funny how people project.
- gigatexal 7y agoI do a lot of work related experiments at home for my own learning and to help what I do for my employer.
- sharpneli 7y agoWhenever I'm having a remote day yes. Some projects can take literally hours to fully recompile. The more cores, the better. Will also be getting a Ryzen if the singlecore benchmarks show it's reasonable. Bunch of games I play at home tend to absolutely trash single core perf.
- m0zg 7y agoWhy do you "fully recompile"? Use Google Bazel and never fully recompile anything.
- sharpneli 7y agoBecause debugging and making changes. Trying to get some centralized server to produce just the right combo of Windows sdk and msvc (Just an example) would take even more time. And then there is the hassle of setting it up for all the possible projects one might work on. EDIT: Just some examples. Instead of developing electron application think of making changes to chromium. Instead of depeloping Qt application think of developing Qt itself. Etc etc.
- m0zg 7y agoEven so, with a proper build system you shouldn't need to recompile. That said, I don't think Windows has what I'd call a proper build system.
- sharpneli 7y agoOne needs to recompile with a brand new checkout. Most of the time buildsystems work. Including one in Visual Studio. But I have never encountered a system that would always work flawlessly. From time to time one gets things like changes not detected or something else going haywire and one has to do make clean and just redo the whole thing. Another thing is when your'e doing profile guided builds then one has to do a full rebuild after each profiling run.
- m0zg 7y agoNot with Bazel (on Linux or Mac at least). It builds everything incrementally. If inputs that go into the build node did not change, they won't be rebuilt. You almost _never_ fully recompile, and with a cache incremental builds almost never take more than a couple of minutes. Google builds everything it runs from source, including things like compilers, runtimes, stdlibs, etc. Imagine if every engineer had to rebuild everything from the kernel up from source on every check-out. That wouldn't work.
- gambiting 7y agoUhm, yes? What else would you do work on at home? On a laptop, with its shitty position for the head, back and the hands? I do have a laptop but that's purely for entertainment - my work is done 100% on a desktop, both at home and in the office.
- paranoidrobot 7y agoLaptops with Thunderbolt 3/USB-C are pretty great for use with a docking station. I get the advantage of having nice large monitors, proper clicky keyboards and mice, and the ability to charge/power the laptop - all over one cable. When I want to move away from the desk - unjack and keep going.
- dmix 7y agoPretty much everyone I know uses laptops at home which is why I was curious. I've always wanted to try out a home PC build for work at home w/ linux. But it's just easier to keep using my work Macbook Pro for everything. Also I always connect it to a large monitor + mechanical keyboard both at work and at home for any serious work... so not sure why you mentioned the neck/hand position.
- dewyatt 7y agoI work pretty much 100% on my desktop at home every day. Only reason I'm on a laptop right now is because of a power outage.
- WC3w6pXxgGd 7y agoWhat will you be doing that will actually use 24 threads?
- ubercow13 7y agomake -j24
- vetinari 7y agoBe sure to have enough RAM, so you will not run out of it. (For some reason, when building projects like LLVM with -j 16, 32 GB w/o swap may be not enough. With -j 2, it is enough, but takes an eternity).
- nikic 7y agoIf you build LLVM often, use the shared library build (BUILD_SHARED_LIBS=true). Most of the memory usage (and a large part of the time in incremental builds) comes from linking final artifacts if you do not use shared libraries.
- vetinari 7y agoThanks for the tip, unfortunately, when I'm building it (occasionally), the LLVM itself is part of another project (AMDVLK) and changes too.
- gigatexal 7y agoThe initial plan is for a 32GB (2x 16GB sticks) with plans to move to 64GB when possible.
- 0815test 7y agoIndeed, if you're bottlenecked on RAM, memory bandwidth itself will also be an issue (it seems to be the foremost bottleneck in modern compute, outside of single-threaded workloads. Part of why C-like languages are again becoming popular these days - they economize on memory-bandwidth per core). Might want to skip Ryzen 9 altogether and wait until the Threadripper parts are announced.
- gigatexal 7y agoball parking the build in my head: - Ryzen 9 or Ryzen 7 - 32GB ddr4 - RTX 2070 or equivalent Navi for games* (depending on benchmarks and if I decide to actually do anything with CUDA) - everything else I have, NVMe system drive, case, PSU etc * Vulkan is big in the games I am targeting: Rage2, Doom Eternal