Try kilocode - https://kilocode.ai/ Its a VScode extension and allows different LLMs to be used.

Thanks for sharing that.

Presumably if you'd split the elements into 16 shares (one for each CPU), summed with 16 threads, and then summed the lot at the end, then random would be faster than sorted?

I don’t think random should be faster than contiguous access, if you parallelize both of them.

Although, it looks like that chip has a 1MB L2 cache for each core. If these are 4 Bytes ints, then I guess they won’t all fit in one core’s L2, but maybe they can all start out in their respective cores’ L2 if it is parallelized (well, depends on how you set it up).

Maybe it will be closer. Contiguous should still win.

What if you factored in time to sort them first?

Ice blocks were trialed in the past. https://en.wikipedia.org/wiki/London_Underground_cooling#cit...

This is a regressive view. Developed countries profit from the educational nature of the Internet. We're all better off from having banked and shared common knowledge.

Ceph is massively over-complicated, if I had two teams I'd probably try and write one from scratch instead.

Most of the legitimate datacenter-scale direct Ceph alternatives unfortunately are proprietary, in part because it takes so much money and human-expertise-hours to even be able to prove out that scale, they want to recoup costs and stay ahead.

Minio is absolutely not datacenter-scale and I would not expect anything in Go to really reach that point. Garbage collection is a rough thing at such enormous scale.

I bet we'll get one in Rust eventually. Maybe from Oxide computer company? Though despite doing so much OSS, they seem to be focused around their specific server rack OS, not general-purpose solutions

> I bet we'll get one in Rust eventually. Maybe from Oxide computer company?

Crucible is our storage service: https://github.com/oxidecomputer/crucible

RFD 60, linked in the README, contains a bit of info about Ceph, which we did evaluate: https://rfd.shared.oxide.computer/rfd/0060

Fascinating! I thought you were using RAIDZ3 with some kind of clever wrapper (or just DRBD), but it’s much more complex than that.

It's not an area I personally work on, but yeah, there's a lot going on. And there will be more in the future, for example, I believe right now we ensure data integrity ourselves, but if you're running something (like Ceph) that does that on its own, you're paying for it twice. And so giving people options like that is important. It's a pretty interesting part of the space!

The 3FS chunk engine is written in Rust.

I thought PostgreSQL did, but now that I check the docs, you are correct, the default `commit_delay` is zero. That would be worth increasing a little if you can afford the latency.

It works even with that setting at zero! Just requires a bit more concurrency.

How is it low res when the specs say 5120 × 2560?

Because the text isn't displaying directly on the headset screen. It's being displayed as a 3d pane within the virtual desktop: https://roadtovrlive-5ea0.kxcdn.com/wp-content/uploads/2016/...

So the actual number of pixels used to display the pane containing your text is maybe 10-20% of the headset display's resolution.

I suppose you could display text directly on the headset display. But then you only have 2,560x2,560 pixels per eye, fewer pixels than a 4k display.

Parent was talking about screen density, so pixels per degree. This headset ~~has more pixels~~ but also a wider fov, so it should feel similar.

Edit: fell for their lies, the headset is only 2k per eye. The 5k figure is "combined", i.e. a marketing number.

I'm with you though: early headsets were low resolution but these modern ones are not. We can still use more pixels though, esp. for text work.

Additionally, the magnetic shape and location of the poles are also shifting, which I think suggests the core is also shape changing.

In this case, it's not directly related. The inner core isn't what causes the Earth's magnetic field. It's convection within the liquid outer core that gives us a strong magnetic field. The inner core changing shape wouldn't necessarily cause changes in the Earth's magnetic field.

Not a lawyer, but why not use opensource as an example? Many successful public e-commerce websites have public schemas and aren't all hacked.

But its a weird distribution, because of owners who never have a single problem.

I mean, all that proves is that there exist _instances of the car_ which are not defective. Like, it would be extremely odd if every single unit was notably defective.