fphhotchips
Joined 13 years ago
Joined 13 years ago
I mean, everything is representative if you just phrase the bits you don't want to do as "some trivial op". By this logic, Clickbench is a great and totally representative benchmark because joins are also trivial ops.
Billions of dollars are spent processing semi-structured data. It's a critical part of most analytical pipelines. You can't just ignore it and pretend like your benchmark is representative.
I've spent years of my life running TPC benchmarks. They're useful guidelines, but they're simply not diverse enough to show the whole picture unless your picture is very simple. Certainly no single TPC benchmark in isolation. Maybe you can get a better idea by running all of them.
The largest gaps are around non-relational style data, JSON querying and the like. Nearly every organisation has something in that space now, and TPC-H/TPC-DS don't touch it at all.
Interesting! I found them mostly ok, but I was playing with a keyboard. They definitely remind me of the controls of Pacman games I grew up with where (as sibling comment notes), you have to decide where you're going before you get there.
I wonder if tweaking the input buffering or adding some frames after the turn where you 'snap-back' would help, similar to ghost jumps in Mario.
I can't even begin to think about how a laptop screen upgrade would go. Who's manufacturing them? How do I get just one? How do I make sure I don't spend a month waiting for shipping and get a fake? How do I make sure the housing is going to fit right? How do I make sure the pin outs match?
... and etc etc. An official upgrade pathway eliminates all of that. Sure, it's not bringing you back to "average person", but Framework have been super clear that's not who they're after. They want people in my bracket. To be honest, as a cohort, we've proven we're willing to (over)pay for this kind of thing, too. It's why the PC Market still exists despite graphics cards being overpriced by about double.
The position thing is just something you get used to. There's not that many reader models in active use and most of them are pretty good about marking where the nfc reader is these days.
You might, maybe, but an increasing proportion of developers:
- Don't have access to the assembly to debug it
- Don't even know what storage tech their database is sitting on
- Don't know or even control what CPU architecture their code is running on.
My job is debugging and performance profiling other people's code, but the vast majority of that is looking at query plans. If I'm really stumped, I'll look at the C++, but I've not yet once looked at assembly for it.
Perhaps it's just because I'm not Dutch.
Some places in Melbourne get real work done, even in the data sector. They're hard to find, but they exist.
I work in performance - a space where we're thinking about threading, parallelism and the like a lot - and I often say "I want to hire who play with trains". What I mean is "I want people who play Factorio", because the concepts and problems are very very similar. But fewer people know Factorio, so I say trains instead.
I think I know why it's enjoyable even though it's so close to work, too. It's the _feedback_. Factorio shows you visually where you screwed up, and what's moving slowly. In actual work the time and frustration is usually in finding it.
The Downer family have recent history in misjudging what "most people" in significant chunks of the Australian public think. Chunks, for example, like the electorate they're trying to be members of parliament in.