Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It really depends on where you sit in the stack.

The generally useful rule is “measure before acting”.

There are some rules of thumb at every layer:

If you’re getting bad scrolling in a web application on a mobile phone, something is probably getting called over and over

If you’ve got an x86_64 server maxing out but the cores aren’t printing work? Zen4’s northbridge has some edge cases.

If you’re trying to melt aluminum so that exquisite optics can do extreme ultra-violet litho: weak hyper charge is very well determined empirically but there are some weird readings on muon spin.

I’m sort of kidding because this is an Endless Internet Feud, but really it’s measure and whack the hot spots.

I’ve done a bunch of this shit: if you’re not sure where to start feel free to email.



This, measure and understand before you start messing with anything in code or infrastructure.

Lots of great resources in this thread, but as the saying goes; knowing is half the battle.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: