|
|
|
|
|
by ascv
2323 days ago
|
|
It's still a huge whoosh. You're starting at 1.9 and you're testing 4 micro versions to 1.10.. what is the point of that? None of those non-major versions are going to significantly change how the GC works. They could have tried 1 other version (not 4) and picked either the latest (1.13) or the version that contains the GC improvements (1.12) to test. Usually when you are looking to upgrade something you skim the release notes so testing 1.12 or 1.13 is obvious especially when 1.12 seems to specifically address their performance concern. If upgrading something avoids a service re-write that is usually the way to go unless you were looking for an excuse to re-write the service in the first place which may have been the case. edit: It turns out they did exactly what my comment stated: they tested the latest version (1.10). It's just that this article was published recently but the events happened quite a while back. |
|
Maybe it does, maybe it doesn't. Maybe 1.14 has a performance regression with their specific load and they get screwed.
We'll never know. You know why? They permanently solved their GC problems by eliminating GC.
That's the smart play.