News for hackers. Stuff that matters.
Re:Reinventing Back End Subsetting at Google by flowblok on Monday December 19, 2022 @05:42AM (#34050630)
> For instance, in table 3, it looks like they excluded backend tasks {0,1} (for frontend tasks {0, 1}) then {2,3} (for frontend tasks {2,3}) in the N=10 case, but backend tasks {1,2} then {3,4} in the N=11. Why the discrepancy?

With N = 10, there will be N mod k = 10 mod 4 = 2 leftover tasks, and so the round-robin fashion excludes {0, 1} then {2, 3}. However for N = 11, there will be N mod k = 11 mod 4 = 3 leftover tasks, so the round-robin fashion excludes {0, 1, 2} then {3, 4, 5}.

But as joatmon-snoo correctly said, the more important point is demonstrating how bad backend churn is with this algorithm.

Re:Reinventing Back End Subsetting at Google by kerneis on Monday December 19, 2022 @07:26AM (#34051266)
OK, that makes a lot of sense. Thanks for taking the time to clarify!

> But as joatmon-snoo correctly said, the more important point is demonstrating how bad backend churn is with this algorithm.

Yes, again the overall point came across clearly, but faced with specific examples I like to dive into the details to check my understanding of how things work. Otherwise, it's easy to overlook key but subtle details.