1,121 karma · joined November 25, 2016
For a thoroughly enjoyable read I'd also recommend The Comedians.
This being said, at least some years ago, a use case I saw that held SOME water then was generating MyISAM tables offline, importing them as-is into a running MySQL (or taking an instance offline and bringing it back up) and then serving from it read-only. At least at the time, this provided better RO performance than InnoDB. I wouldn't be surprised if that was still true. Please don't do that at home!
Also, I think until the previous-to-most-recent release, some internal tables were still MyISAM, causing MySQL overall to have some very rare cases of not being crash safe. Again, I think that's since been resolved in 5.8(?).
Don't use MyISAM!
I know, hardly authoritative. But it matches precisely what I remember from when I was hacking on perl with an eye to performance at the time.
Maybe drop that bit regarding 'register'? The rest of that section is still perfectly valid. That is, assuming the compiler doesn't actually perform the local variable/keep in register optimisation itself, but I think it can't do that at least in the general case. I only remember vague things about this. At least aliasing may defeat the compiler optimisation.
Caveat: Like yourself, I picked this stuff up without studying it as part of a degree. Anybody with a proper compiler background want to jump in and enlighten maybe?
Hmm. I may be getting rusty, but do modern compilers actually still pay attention to the "register" keyword?
Also, I may have read this too quickly, but if I'm not mistaken you limit the number of parameters to 8, yet the number of arguments passed to 255. Does that make sense?
Thank you once again for a brilliant read!
Have you read The Maglev paper out of Google? At the time right before that was published, one of my engineers was implementing much the same thing. They considered both HAProxy and nginx for the second layer of load balancing. The were technical reasons in either direction. There was some pressure (from me) to go with nginx because we were already using it as our primary webserver, so we could avoid introducing another new technology for people to master.
We went with HAProxy. Why? Because when said engineer contacted them, describing what he was doing, they (here: the main HAProxy dev) engaged in discussion, helped, even included his needs in their planning. At least at the time, nginx folks just responded with that they'd talk to him after he had secured a licensing deal. The uphill battle this engineer would've had to fight in corporate politics to get licensing sorted out that early in the prototyping phase would have been rough. Last I heard, the company still had a licensing/support deal with HAProxy.
Good presales matter!
(Edit: can't spell.)
The type of work, though, and skills required are quite different, regardless of that they technically both develop and involve 'technology'. Semiconductor lithography requires a pretty exciting mix of skills starting with plain physics (classical and by now a bit of quantum optics), materials science, mechanical engineering, data analysis/science, software engineering (both for simulation and analysis of production of lensing systems), and I'm sure I'm missing half. It is quite different from "writes software for a software company", which is the framing I had interpreted from the comment I originally responded to.
There's perfectly ample evidence for cosmic rays (ie. high energy radiation from astronomical sources) increasing risk of cancer as does any ionizing radiation. Maybe GP conflated the two?
The particle physicists in the collaboration were by and large against calling it a discovery. The astronomers (by and large) shared your sentiment about the particle physicists being curious folk. :)
This was among the most breathtaking things I've ever seen (the other being a particularly vivid showing of northern lights in Alaska). The southern hemisphere's sky is infinitely more exciting than the northern one.
If your income as a Google engineer is so tight that you have to make sure you get the most out of breakfast and dinner, go for it (but also maybe have a long hard think). The culture may well vary between sites, but this idea that Google (and others) exclusively employ fresh college grads and try to embrace then 24x7 just isn't true. We have families just like anyone else, and they matter to us every bit as much as everyone else's families matter to them.
I for my part am happy that I get a healthy, hot meal for lunch so dinner can be a quick snack when I get home, so I have more time with the kids. The alternative is more time spent on chores.
Please stop spreading these tired tropes.
This is very much aligned with the direct cost and services provided. Attending German universities is virtually free, and under certain conditions, the country will give you very cheap loans to pay for your living expenses. My spouse had a single digit number of thousands of Euros to pay back after graduating.
PhD students are often underpaid employees and are treated that way (for better or worse) instead of being considered as and treated like students. This doesn't imply one is preferable to another, just that it is a continuation of treating them with and expecting a higher degree of maturity and independence.
An upshot for me was that when I applied to my first industry job, the time as a PhD student was treated as work experience.
So yeah, I think you're spot on in that many folks from continental Europe would find the amenities bewildering. :)
The physical&power infrastructure side of big data centers is really quite interesting, by the way. Not something we all get exposed to regularly but I can only encourage anyone who has a chance to learn about it to take that opportunity.
My knowledge is from another industry that relies heavily on backup generators.
Back in 2007, I was writing my diploma thesis (think master's just twice as long, German system prior to bachelor/master) at Auger. The collaboration has a rule that for the first year in, you don't go into the author list, but stay on it for a year after you leave. That optimizes for having the actual contributors on papers. Towards the end of my not-on-the-papers year, the collaboration published a really big paper on correlations between the arrival directions of the highest energy cosmic rays, and certain objects, active galactic nuclei (giant black holes at the center of other galaxies). This didn't just get published in Science, it made it to the cover. It was a step towards working out where these mysterious particles are coming from, and what mechanism might possibly exist to accelerate them to such energies! I was kind of bummed not to have my name on that paper (though even at the time thought the one year rule made sense).
The publication had been hotly debated internally. It had received all conceivable internal scrutiny (the author list contained over four hundred names). There had been a stark debate about what the right statistical significance was for claiming a discovery. Astronomers were used to less rigorous requirements than the particle physicists that together made up the collaboration. Ultimately, it was decided to claim a correlation. (A nil result would have been published as well.)
Almost from the day of publication, the statistical significance of the result, but in data continuously collected since, started to diminish. I was involved in running the nightly data reconstruction, and often times we would huddle around one of the workstations on the morning, to check whether a new high energy event increased or decreased the significance. It kept going the "wrong" way.
The collaboration went into a frenzy to double check everything. They redid the calculations, checked all hardware (a field of water tanks and electronics 3000km^2). Had lots of internal conferences with heated debates.
Ultimately a note was published describing the staggering decline of significance. If I remember correctly, my name was on the author list by then and I got to joke that I knew it all along.
I'm no longer in the field. Since then, the collaboration has published a di-polar asymmetry of the arrival directions of the highest energy cosmic rays. That proves something we already pretty much knew: these are not particles from our galaxy. That was a meaningful discovery. But I'm not aware of a publication with as exuberant a discovery as the source correlation.
Happy to expand on my experience if that would be helpful.
In the book, Bob says he designed the language such that it would be possible to use just one stack. What does that mean? It sounds very discouraging for newbies because it implies a lot of foresight or trial and error.
Overall, while this is among the most interesting subjects covered, I find the chapter a bit lacking in either one of two ways: either it is for beginners, and then the chapter feels very magical or is for intermediates and then a bit of extra verbiage on the design choices that led you there would be appropriate.
Nitpick: I would totally have stopped low and done the -1 initialization trick as well. But yuck. ;)