I'm running systemd on my cellphone right now, and I also have installed, for example, Firefox, LLVM, the Whisper speech recognizer, and PARI/GP. It sounds like you're implying that the amount of code is unwarranted by the functionality, but he hasn't told you anything about the functionality, only what platform it runs on, which is mostly irrelevant to the functionality.
This happens in most systems programming languages by default, but it's cool to know it happens in postgres too. Iirc wasn't it zig or some compiler that had some speedup or optimization just by arranging fields around? I may be wrong
TANGENT WARNING: What bothers me is that unless you are directly plumbing data on disk to the wire, there is literally no benefit to serializing data this way. (I originally realized all this when trying to add varint and byte types to postgres to make storage more efficient, and then finding it was almost impossible to actually serialize them in a way that saved space)
At runtime, if you've allocated a boolean or want to store a byte somewhere, you've either done it on the stack (it's temporary and you know it will need to be accessed at least once as an independent unit of data, and packing it together with other small data structures will make you use an extra instruction to extract it into its own register anyway, so there is not really any benefit to packing them tighter) or heap (you might actually gain something by reducing memory usage here, but packing data together binds the lifecycle and structure of everything at the same address and either requires additional lookups to check the interior structure, or a fancy compiler/build process to bake in the instruction to extract packed data without knowing what other data is packed with it).
When you read serialized data for a record from the disk, while running a typed database, the lifecycle/structure within the record is already shared. Most times you load the record you probably won't be accessing any particular packed data structure (eg if you have 5 bool columns in a table, most queries won't use all or any of them). You already have a global way to handle internal types/optimized reads, because that's what databases do.
So it would actually be feasible to load packed data and efficiently access or calculate with it eg XOR against 0x00..00 to use a bool, or bit shift to load a subword into a register. It would be at worst 1 instruction per read slower if implemented efficiently (the query planner can handle the type lookup/deciding how to do the optimized read, which amortizes and isn't the query bottleneck or even on the critical path).
BUT denser data = more cache coherency and higher read throughput (more rows/s). And if you're doing fancy bit operations and arithmetic to extract and perform calculations on the packed data, it might actually be easier to batch operations with SIMD. So you could get arguably higher performance + much less passive disk usage (saving actual money) by packing data better probably. I'm about 30% of the way towards convincing myself to try this
I was referring to those big shop heaters that use forced-air propane, butane, or kerosene to generate massive heat. But yes, there are electric heaters too. It wasn't too annoying, just opinionated and misinformed.
Databases licencing per core is the most ridiculous thing I've heard for me. In this case they have zero marginal cost and still charge you for it. Hilarious.
> In this case they have zero marginal cost and still charge you for it.
A license has zero marginal cost in the first place. Software distribution over networks have a negligible marginal cost. An ebook as zero margin cost. We are constantly paying lots of things with zero or negligible marginal cost.
These deals aren't as slimy as they look. Yes, there's no marginal cost, but the goal is to spread out the costs as evenly as possible with the companies using the software. Setting the price per core just means that the companies that might do more processing shoulder more of the software cost. (And, yes, it's another way to gouge companies. But it's gouging based on use.)
Not necessarily slimy. The problem is that there is no clear right pricing where there is no marginal cost - makes it hard to decide whether the pricing if fair or not.
Even for things like the huawei ascend, what makes them crap for price to perf I think is still dram. They actually cost more than nvidia clusters last I checked. Just like how regular laptops and phones are now being squeezed upwards to become closer (and uncompetitive with) apple devices.
This reminds me of the (perhaps unrelated meme) hello I would like (graph of zeta function) number of apples. Statements dreamt up by the utterly deranged.
Indeed I have met professors who claim since something is O(1) it doesn't matter if you run it 4 times. No need to optimize. I think it's just part of the wider divide between theory and application. For instance big O also requires a register machine to make sense, which most courses don't define. Somehow addition and multiplication are O(1) in some places and O(n) or O(n^2) somewhere else. Also quite common is the fact that sets are slower than lists for lookup for small n, despite being O(1).
It's just a tool and we shouldn't miss the trees for the forest. I also understand this comment has nothing to do with the ETH or the article, but just some thoughts I have after reading the first chunk on complexity
Did you ever pause to consider that theoretical computer science might not be done for the sake of midwit code monkeys whose deepest contact with complexity theory was when they learned to reverse a linked list in O(n) for their SWE interview?
I'm not sure that retreating to the ivory tower is a winning rhetorical strategy.
Not sure why the hostility anyways. If appreciating TCS results really is a higher brow activity, then GP's indignation at computational models shouldn't upset you, quite the opposite. It's definitionally the normal experience.
And while I do find the blogpost in the OP trite, that is mostly because it's from someone who should absolutely be more intimate with the subject than such "midwitted code monkeys" (aka. normal people) you refer to, yet pretends to feel duped by OAI's results. Quite the different case, and I think is much more worthy of ridicule as a result. They're the high brow who should be appreciating, understanding, yet fail to.
I think the common expression is to miss the forest (big picture) for the trees (details). But maybe you're playing on words and saying we shouldn't let the big picture (big O notation/analysis) obscure our attention to the details (an algorithm's actual efficiency and performance).
Does this actually work. There's no way to say apple with your mouth closed. At least it doesn't feel correct. Feels like what comes out is closer to "Ethan"
reply