3 ms·
A common developer scenario can involve a few things that will eat a lot of threads: 1. playing some background music 2. running a local database 3. running a
by gameswithgo 7y ago
A common developer scenario can involve a few things that will eat a lot of threads:
1. playing some background music
2. running a local database
3. running a local webserver
4. running a browser
5. running an ide
6. running all of that stuff concurrently while testing the backend code
7. doing builds which are multi threaded in near linear speedup fashion in many languages/environments.
I don't know if 12 cores 24 logical is going to make that scenario feel overall better than 4 cores 8 logical, but I do know that 4x8 feels much much better than 2x4 in my own use cases.
#7 alone can be a really, really big win for long compiling projects.
- gigatexal 7y agoThis. But to the OP's main criticism: I could very well do all of that with 16-threads and 8 real cores. I do a lot of work currently with distributed databases and I believe I need the cores for local testing along with everything else that gameswithgo mentioned.
- dkersten 7y agoYeah, my docker setup alone runs a ton of processes. Aside from docker running a copy of my stuff, I often have tests auto-running, a separate REPL to try stuff out in, my editor, slack, music, browser. It all adds up and a bunch of cores/threads definitely makes everything run more smoothly.
- Traster 7y agoCommon developer scenario: make -j24