News for hackers. Stuff that matters.
Re:Sub-millisecond GC pauses in Go 1.8 by countingteeth on Tuesday November 01, 2016 @08:33AM (#12845094)
No. The entire premise of amortized analysis is to get a more optimistic "eventually O" number. "Eventually" is not good enough for real time. Yes you can get a real hard worst-case number, but that's a different analysis from amortized analysis. Unless all of your amortized operations are happening between deadlines, it's useless--worse, dangerous--for safety. And amortized analysis is almost never used that way. You don't have language run-times that reinitialize between every deadline.
Re:Sub-millisecond GC pauses in Go 1.8 by lomnakkus on Thursday November 03, 2016 @03:25PM (#12867132)
You're right.

I somehow confused myself by thinking of it in terms of one of the proof techniques for amortized worst case where you derive a fixed upper bound for any "n". Of course this is a much stronger property than needed.