Hacker News new | past | comments | ask | show | jobs | submit login

You can almost always go back to mainframe for inspiration - back in the day they pretty much solved every problem you can think of. It has just taken 40-60 years to be able to do the same thing on consumer class hardware.

Last I checked there was still no mechanism where I could bill back resource usage in a multi-tenant kubernetes cluster so I think there is still work to do.




We aren't fully there yet, some of them like Burroughs, were already using quite safe systems programming languages.

ESPOL/NEWP were most likely the first ones to have unsafe blocks, as I think JOVIAL lacked them.


> bill back resource usage in a multi-tenant kubernetes cluster

I feel a bit dumb for asking, but what about process accounting? I'm not sure if it can deal with RAM and I/O, but it's better than nothing. (https://linux.die.net/man/8/sa)


> bill back resource usage

If you are not oversubscribed, you can just count the allocation.

Maybe performance counters can help. How long does it take to read op counts prior to a context switch?




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

Search: