The only interesting thing would be to see how much of a performance improvement each of the separate changes brought.
Phrases like "Most of the time was spent by the server to compile the necessary dataset of time entries, but also related data." seems to hint at:
a) missing profiling (was it database queries, actual computation, network I/O, disk I/O, ... ?)
b) architectural problems (a database schema that didn't perform, missing indexes, ...)
I'm sure Go is a nice language, but I don't see how Go could improve any of those besides maybe a more managable approach to parallel computations.
Given the amount of seemingly parallel changes that happened, it's pretty much impossible to determine what actually caused the improvement (at least with the information in this blogpost).
Phrases like "Most of the time was spent by the server to compile the necessary dataset of time entries, but also related data." seems to hint at:
a) missing profiling (was it database queries, actual computation, network I/O, disk I/O, ... ?)
b) architectural problems (a database schema that didn't perform, missing indexes, ...)
I'm sure Go is a nice language, but I don't see how Go could improve any of those besides maybe a more managable approach to parallel computations.
Given the amount of seemingly parallel changes that happened, it's pretty much impossible to determine what actually caused the improvement (at least with the information in this blogpost).