Seconded enthusiastically. That dam tour is amazing. Did it in 2007 or so.
Expect potential weirdness though. My wife was wearing a (not particularly short) skirt, and the lady at the office selling tour tickets made her step back and spin around, then said she couldn't go in like that. There is a gift shop that sells dam branded pants, so she bought a pair and we were cleared to go in. After all that, one dude in the control room was watching soft-core porn on one of the control room computers.
The turbine shaft room is especially crazy, since they let you (at least back then) walk right up to a few inches away from the shaft mechanically transmitting 700 MW of power! You could reach out and touch it, but we didn't and I wouldn't recommend it.
Intel, at the time the unquestioned world leader in semiconductor fabrication was so unable to accurately predict the end of Dennard scaling that they rolled out the Pentium 4. "10Ghz by 2010!" was something they predicted publicly in earnest!
I arguably owe a successful career in tech to my dad seeing a $99 deal on a TI-99 after they were discontinued in the mid 80's and buying it just because he had had a shortwave receiver as a child and saw some weird similarity. Unbeknownst to him, it turned out my mother had been a FORTRAN programmer in the 70's (though she described it as working as a lab-tech in a bio lab), and taught me how to program it in its weird BASIC dialect.
I've never understood why Intel didn't just soft-disable AVX512 on P-cores until the OS writes a value to some MSR that means "I understand that only some cores have AVX512".
From the OS side, the change to support it is pretty simple. On the first #UD trap caused by an AVX512 instruction being missing, pin the process to just the P-cores and end the process's timeslice.
It comes with a dedicated remote (though it does support CEC), which solves #1, at the cost of having an extra remote.
I mainly hit #2 when scrubbing, often (worse on some compression types than others), it'll just freeze frame for a minute before everything catches up. This may be because I'm serving the content via HTTP to the Vera V, I've been meaning to try NFS and/or SMB. Never had issues with playback itself, probably because the Vera V hardware and the OSMC/Kodi build are co-developed, so there is pretty much always hardware decode support.
#3 surprised me; Kodi supporting just using my directory layout is why I use it over something like Jellyfin! I just added the HTTP share, and then navigate Videos->files->my_http_share_name and I'm in my directory structure.
Most of the Intel cache partitioning things were driven primarily by Google. The holy grail was to colocate latency-sensitive tasks with bulk background tasks to increase cluster utilization.
It is also the only way for an xlib program to survive losing its connection to the X server. xlib will let you register a callback to handle loss of connection with XSetIOErrorHandler, but unconditionally calls exit() after your callback returns. Which is extremely anti-social behavior for a library, but that is what it does.
So the solution is to setjmp before each call to an X function that might notice the connection is closed, and longjmp out of the error callback. Ugly, but it works.
These days, you should really just use XCB, or even Wayland.
Expect potential weirdness though. My wife was wearing a (not particularly short) skirt, and the lady at the office selling tour tickets made her step back and spin around, then said she couldn't go in like that. There is a gift shop that sells dam branded pants, so she bought a pair and we were cleared to go in. After all that, one dude in the control room was watching soft-core porn on one of the control room computers.
The turbine shaft room is especially crazy, since they let you (at least back then) walk right up to a few inches away from the shaft mechanically transmitting 700 MW of power! You could reach out and touch it, but we didn't and I wouldn't recommend it.