knz42

9 ms·

31.
by knz42 5y ago
> The expansion of pclntab in Go 1.2 dramatically improved startup time and reduced memory footprint [...] yes this is acknowledged in the OP > We (the Go team) did not “recompress” pclntab in Go 1.15. There's now less redundancy
32.
by knz42 5y ago
This 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.
33.
by knz42 5y ago
This code, if I'm reading it right, uses the symbol table and ELF section headers. As explained in OP, the sum of sizes advertised in the symtable and ELF section headers does not add up to the final binary size. The shotizam tool is t
34.
by knz42 5y ago
> But still, the sum of all the bytes advertised in symbol tables for the non-DWARF data does not sum up to the stripped size. What's the remainder about? if you do know, then pray, what is the answer to this question?
35.
by knz42 5y ago
Strip removes the symbol tables and DWARF information. But still, the sum of all the bytes advertised in symbol tables for the non-DWARF data does not sum up to the stripped size. What's the remainder about? I am reminded of how early
36.
by knz42 5y ago
As explained in another comment below, it's a good thing when all the byte usage is represented in the ELF section headers or the symbol tables. The DWARF data is currently so represented, and so was pclntab prior to 1.16. Today, the D
37.
CockroachDB's PR Organization Philosophy(wiki.crdb.io)
3 points by knz42 6y ago|0 comments
38.
by knz42 6y ago
How does this compare to https://onlysponsors.dev/ ? HN discussion here: https://news.ycombinator.com/item?id=25882021
39.
by knz42 6y ago
They can't require things that have a direct impact on the employee's private life, so contraceptives and anti-psychotic drugs are out. They can't require things that have unknown medical impact, so random pills out. (However
40.
by knz42 6y ago
You're mis-reading the text. The reduction in cost pertains to the try/catch (defer/recover) mechanism, not error returns. The cost of error returns has not reduced since Go 1.10.
41.
by knz42 6y ago
This was clarified in the conf talk [1] [2]: error returns should be used at API boundaries, and panic-driven handling only "within" a component. [1] https://www.youtube.com/watch?v=inrqE0Grgk0&t=15126s [2] h
42.
by knz42 6y ago
FYI these results were presented at the Go Systems Conf SF last December: https://www.youtube.com/watch?v=inrqE0Grgk0&t=15126s
43.
by knz42 6y ago
Absolutely yes.
44.
by knz42 6y ago
And yet it certainly is there.
45.
by knz42 6y ago
> that the actual performance cost for checking the error return is random, variable, and small. Good to know :) That is certainly not the article's conclusion. The cost is deterministic, constant and non-negligible.
46.
by knz42 6y ago
The report says that AWS's ARM-based Graviton2 cores were tested. Where can we find the download link for the CockroachDB release that was used to test on ARM?
47.
by knz42 6y ago
You need to integrate transaction coordination with replication to ensure that the replication respects transaction atomicity (so that cross-shard queries get all their reads and writes isolated from each other, and rolled back atomically w
48.
by knz42 6y ago
I wasn't sure. Thanks for checking. three years is a negligible amount of time.
49.
by knz42 6y ago
> How compatible? That is literally explained in more than 40% of the article.
50.
by knz42 6y ago
BSL is "delayed free software". Take the code, wait 3 years, then it's entirely free software.
51.
by knz42 6y ago
This article reads odd to me. It seems to me that serious players do not compromise on these things at all. For example, CockroachDB ( https://www.cockroachlabs.com/ ) aims to support extremely large databases in a distribut
52.
by knz42 6y ago
For folk who prefer a video to text, I found the following high level explanation on Youtube: https://www.youtube.com/watch?v=wdv8uvDhbcQ
53.
CockroachDB Code Commenting Guidelines(wiki.crdb.io)
3 points by knz42 6y ago|0 comments
54.
by knz42 6y ago
The technology is open source though. (Its BSL license automatically switches to APL after a year or two.)
55.
by knz42 6y ago
https://www.cockroachlabs.com/docs/stable/make-queries-fast....
56.
by knz42 6y ago
> It seems like an argument against all kinds of transactions that are linked to irreversible side effects, regardless of whether any are nested. Correct. The best design is small transactions without side effects. The problem with the
57.
by knz42 6y ago
Author here - yes there are schemes to do it client-side. However there is enough legacy code and frameworks out there that use nested transactions via pg's savepoint protocol, that some compatibility with those is warranted.
58.
by knz42 6y ago
They do - sometimes.
59.
Ubuntu without Snap – how to fix(dr-knz.net)
3 points by knz42 6y ago|0 comments
60.
by knz42 6y ago
What is the story behind the removal of VLAs from C99 in later revisions?

More ›