I try to tell my brain that, but it doesnt understand. I have only two speeds apparently. 0 or 100. And my brain loves sitting at 0 until it has no choice but to go to 100 until whatever it is is done.
That is called racing to sleep iirc and is a valid cpu scheduling technique. It works on the assumption that doing nothing (sleeping is the term there) is much more energy efficient than doing anything even if slowly, so much so that you make up the energy spent to boost to top speed.
I can be hella efficient when i need to, and definitely get things done more quickly than i would if i weren’t on such a tight deadline, and when i was in high school or whatever it worked out okay, but as ive gotten older the stress and anxiety has started to impact me more, and now its to the point where even in the downtime i cant actually relax and end up stressing about what i need to do, but cant bring myself to start it.
If you have somebody doing work that can appear at random (like somebody calling and saying they have a problem), that person will either be free for a fraction of time that seem high to naive people, or will have a line and take ages to help anybody approaching them.
That seemingly high fraction of time is usually around 50% for the line to stay under control. That’s a well known result from mathematics.
Counterpoint: but couldn’t they simply do a bunch of lower-priority tasks, whereupon anytime someone needs something from them they can easily drop that and shift over to do that at a higher prioritization? Yeah it’s wasteful for context switching, but it gets the main job done and that’s what matters?
ELI5 version: every new request from an actual human goes straight to the front of the line, or rather to the back of the “human” line, in front of all the “busywork”.
Yes, as long as you accept that the lower-priority tasks get dumped when needed.
This is a common way to deal with it. But the number of managers that know how to decide a task is low-priority is exceedingly small. Most only have top-priority tasks to distribute to people.
Though the absolute best cluster systems I’ve seen have utilized this principle correctly, never leaving it idle, yet never blocking work that others want to do either (for more than a very small amount of time).
Planning such takes a great deal of effort though, and most people seem to simply want to be paid and even more importantly than that feel in control, or perhaps worry that if they don’t rise up beyond their potential to handle matters that their own job won’t be quite as stable. Bc capitalism seems to fuck up everything it touches, more’s the pity.:-(
I try to tell my work that, but they don’t seem to understand.
I try to tell my brain that, but it doesnt understand. I have only two speeds apparently. 0 or 100. And my brain loves sitting at 0 until it has no choice but to go to 100 until whatever it is is done.
That is called racing to sleep iirc and is a valid cpu scheduling technique. It works on the assumption that doing nothing (sleeping is the term there) is much more energy efficient than doing anything even if slowly, so much so that you make up the energy spent to boost to top speed.
I can be hella efficient when i need to, and definitely get things done more quickly than i would if i weren’t on such a tight deadline, and when i was in high school or whatever it worked out okay, but as ive gotten older the stress and anxiety has started to impact me more, and now its to the point where even in the downtime i cant actually relax and end up stressing about what i need to do, but cant bring myself to start it.
Fuck… are you a mirror, cause that’s what I’m seeing right now!:-P
Remainder of the quote: “…I want you to remember me.”
Knew someone in Trek had to have said it.
Any manager that doesn’t know about the utilization/latency trade-off from queue theory is a danger to themselves and to others.
ELI5?
If you have somebody doing work that can appear at random (like somebody calling and saying they have a problem), that person will either be free for a fraction of time that seem high to naive people, or will have a line and take ages to help anybody approaching them.
That seemingly high fraction of time is usually around 50% for the line to stay under control. That’s a well known result from mathematics.
Counterpoint: but couldn’t they simply do a bunch of lower-priority tasks, whereupon anytime someone needs something from them they can easily drop that and shift over to do that at a higher prioritization? Yeah it’s wasteful for context switching, but it gets the main job done and that’s what matters?
ELI5 version: every new request from an actual human goes straight to the front of the line, or rather to the back of the “human” line, in front of all the “busywork”.
Yes, as long as you accept that the lower-priority tasks get dumped when needed.
This is a common way to deal with it. But the number of managers that know how to decide a task is low-priority is exceedingly small. Most only have top-priority tasks to distribute to people.
Sigh… yes.
Though the absolute best cluster systems I’ve seen have utilized this principle correctly, never leaving it idle, yet never blocking work that others want to do either (for more than a very small amount of time).
Planning such takes a great deal of effort though, and most people seem to simply want to be paid and even more importantly than that feel in control, or perhaps worry that if they don’t rise up beyond their potential to handle matters that their own job won’t be quite as stable. Bc capitalism seems to fuck up everything it touches, more’s the pity.:-(
- image source
Q theory, you say?
I think a lot of them don’t know their ass from a hole in the ground.