4 ms·
Here is a question: imagine you could double performance of cockroa hDB by making the executable 2000MB - every db admin would make that choice
by ClumsyPilot 6y ago
Here is a question: imagine you could double performance of cockroa hDB by making the executable 2000MB - every db admin would make that choice
- knz42 6y agoThis is effectively what is happening btw; the crdb binary went from 80MB to 200MB in the same time it took to make it twice as fast. The % growth in size is not a problem on its own; it's more the % size attributed to the program vs. the % size attributed to unclear purposes, that's a problem.
- aflag 6y agoWhat's the use case where a 200MB binary size is a problem?
- knz42 6y agoThe use case where said binary is shipped to GCE instances hundreds/thousands times per day, for stress testing and unit testing of cockroachdb.
- aflag 6y agoIf most of the bytes are indeed cruft, can't you just send binary diffs around? I imagine they should change that much between compilations? It seems to be an issue for db developers but not for users.
- spockz 6y agoYes, if it would double the performance in many cassis, then the size would have a significant benefit. Here we are taking about large binaries without apparent benefit and a drive to keep binaries as lean as possible.