4 ms·
I agree in principal, but they first put it in k8s and then split it into a job queue. They even state that it took over a day to run at one point, implying a l
by orf 3y ago
I agree in principal, but they first put it in k8s and then split it into a job queue. They even state that it took over a day to run at one point, implying a lengthy and prolonged attempt at fixing the issue.
If you’re working on something and it’s slow, and during some iteration cycle you find that changing some lines makes it fast, cool. No need to debug it or spend time digging into it.
And it’s good that it’s faster, the post screams “we don’t know how to debug these issues” rather than “we don’t care why it’s slow”.
- insanitybit 3y agoI think we basically agree, some debugging and profiling was probably warranted here, since they were going to go through the effort of horizontal scaling.