Earlier quoted context omitted.
Nails and hammers are great but most of us have moved on to screws and screwdrivers. What good does it do to stick your head in the sand? CPUs are great for orchestrating work, GPUs are great for actually doing the work.
>"What good does it do to stick your head in the sand?" Get the fuck out. I do write for GPU as well. One does not replace the other.
Explanation of everything you can see in htop/top on Linux (2019)
21–30 of 71 posts
Re: Explanation of everything you can see in htop/top on Linux (2019)
#22[flagged]
If you’re a 3D rendering designer, an ML engineer or a crypto bro, then sure.
Here are the common workloads (for the average SWE on HN) that use CPU/RAM:
- compilation/builds
- language servers and IDEs
- test suites
- local containers
- local databases
- node tooling
- browsers
- data processing
- compression and encryption
- searching/indexing
Ok sure, top/htop is totally irrelevant now /sRe: Explanation of everything you can see in htop/top on Linux (2019)
#23I've relatively recently migrated over to using btop[0], and it's the kind of modern interface, useful and informative, that I needed. As others mention it - it seems to shows the Watts used as well :) (and network, and GPU, and disks,....) [0]: https://github.com/aristocratos/btop
Yup, btop zealot here, it even replaced iStatMenu on my brand new MacBook ..
Re: Explanation of everything you can see in htop/top on Linux (2019)
#24Earlier quoted context omitted.
Irrelevant for you does not mean irrelevant for others
Nails and hammers are great but most of us have moved on to screws and screwdrivers. What good does it do to stick your head in the sand? CPUs are great for orchestrating work, GPUs are great for actually doing the work.
Re: Explanation of everything you can see in htop/top on Linux (2019)
#25Re: Explanation of everything you can see in htop/top on Linux (2019)
#26Earlier quoted context omitted.
Irrelevant for you does not mean irrelevant for others
Nails and hammers are great but most of us have moved on to screws and screwdrivers. What good does it do to stick your head in the sand? CPUs are great for orchestrating work, GPUs are great for actually doing the work.
Right, and wouldn't it be really nice if we could check on our orchestrators to make sure their not bottlenecking ops?
"How come we can fully load the GPUs?" "Idk boss, amelius said htop et al were irrelevant so we can't really investigate"
Re: Explanation of everything you can see in htop/top on Linux (2019)
#27Earlier quoted context omitted.
>"What good does it do to stick your head in the sand?" Get the fuck out. I do write for GPU as well. One does not replace the other.
For high performance work, gpus have replaced cpus a long time ago.
No one's doing database management on GPUs. No one's scraping data on GPUs. Can't run VMs on GPUs. Can't run web servers on GPU...
Re: Explanation of everything you can see in htop/top on Linux (2019)
#28I've relatively recently migrated over to using btop[0], and it's the kind of modern interface, useful and informative, that I needed. As others mention it - it seems to shows the Watts used as well :) (and network, and GPU, and disks,....) [0]: https://github.com/aristocratos/btop