13,578 karma · joined May 15, 2013
More pernicious than ? is . though. Not that it matters in your case, but a lot of matches really can be "oops, a one character substitution totally matches, too".
https://igl.ethz.ch/teaching/shape-modeling/sm2022/
is a course that Olga Sorkine-Hornung taught in the Spring. Seems to have some decent course titles, but apparently the course slides are only available at ETH itself... (anyway, find some other course and dig in!)
Btw, because nobody has said it explicitly yet: you should start at BTrees [1]. As you guessed, the database folks were the primary "we have to deal with spinning disk and it really matters to be fast" people.
There's also the Log-Structured < Noun > universe of things which 'tlb is pointing you at. Roughly, you turn random writes into appends (to a "log"), often followed by periodic compaction to make reads reasonable (since in-place updates to a "file" are now appended at the end of the log, you've suddenly made reads worse).
[1] https://www.greenbuildingadvisor.com/question/what-is-minisp...
Filtering the LLNL Sankey diagrams to Texas (last available seems to be 2019) at [1] sadly doesn't break down the Industrial use, but I'd guess it was for oil wells and such (and I'm disappointed I didn't think about that earlier). The summary at [2] includes the simple quote:
> Texas leads the nation in energy consumption across all sectors and is the largest energy-consuming state in the nation. The industrial sector, including the state's refineries and petrochemical plants, accounts for more than half of the state's energy consumption and for 23% of the nation's total industrial sector energy use.
But both the Sankey diagram and that wording suggest direct use of the energy (e.g., onsite burning of petroleum) and not anything related to the grid. I'm more confused than we began this :).
float* x = malloc(width*height*channels*sizeof(float))
Is x an "Image"? Is x a "tensor"? Is x a "raster"?
For tensors specifically, if x is not itself the product of vector spaces, then it's not a tensor.
tl;dr: While every rank-N tensor can be represented with multidimensional arrays, not all multidimensional arrays are rank-N tensors.
In late 2012 (first submission) tensor decomposition was likely very interesting (the paper has >1000 citations!). But given that this article doesn't distinguish between "use tensors" and "use tensor decomposition, not SVD or similar for old school setups" I think the article is super confusing.
Perhaps the author didn't get the distinction, and decided to write up a "renegade/rebel" piece that is sadly a non sequitur.
[1] https://www.caiso.com/documents/californiaisopeakloadhistory...
Whoa. That's a real mistake. v4.0 is widely considered a "oops, we shouldn't have released this". TIL!
I would assume this person is just doing an in-memory "NFS server" that would keep all of that state around. So it's more like a FUSE-compatible layer that speaks NFSv4 as a "front end" (since NFS clients are better than "ha ha, surprise! This FUSE backend is networked and can fail on weird ways").
I'm not sure how they chose to translate things like DELEGATE, SEQUENCE, and so on (probably just reply with an error). But for basic OPEN, READ, WRITE, etc. it's all fairly straightforward.
I had hoped they used nfs-ganesha for the NFS server / frontend, but the attributions file suggests they probably rolled their own (and thus is going to be full of bugs and immature for quite some time).
Just to be clear, this didn't go very far. It's more like Brendan was willing to write Java, and a lot of other folks hate it. I don't think any of the core folks were Go advocates, just most of "us" were C/C++ people. Docker itself being in Go, meant it would lower a lot of friction, and besides we had great tooling for Go.
tl;dr: It was really "Should we (re)write this in C++? Eh, how about Go?".
We got to go second, but I prefer the naming and separation of concerns we came up with (obviously): Reservations are capacity you're holding, while Commitments are things that get you discounts.
Reservations are things your operations team uses to guarantee capacity for scaling up, doing rolling restarts, and whatever else. Commitments (and Committed Use Discounts) are primarily what your Finance teams work with.
The original Reserved Instance product combined both of these. AWS now has the same decoupling with Savings Plans and Reservations as related, separate products.
In California, roof color isn't regulated, but reflectivity (or rather energy absorption) is by Title 24. You're basically required on new construction to have a fairly efficient roof.
[1] https://www.homedepot.com/p/Henry-4-75-Gal-Acrylic-Reflectiv...
TIL this amusing combo, thanks! The Wikipedia entry is helpful [1]
From the last paragraph before the Conclusion:
> On the Nehalem there is a significant performance differ- ence between the two implementations on both compilers. Even though both implementations have the same instruc- tion order, the compiler reorders the intrinsic implementa- tion, but does so sub-optimally. On the Sandy Bridge the performance difference is slight. We examined the assem- bly code generated by both the icc and gcc and in the two cases ordering of the instructions are not the same as the initial ordering, so the intrinsics do not maintain the order- ing. In the previous experiment (Figure 12) the ordering was not close enough to an optimal one and from the compiler scheduled implementation the compiler did not achieve the same performance as the expert. We suspect that because of its large reorder windows, the Sandy Bridge is less sensitive to the instruction order than the Nehalem.