Git LFS for example does not support file chunking. So a single byte change on a large (100s of gigs) file means downloading the whole file again. Lore does chunking of binary files which means faster downloads and better de-dupping on the backend.
Disagree, but also what do you classify as local storage? Does the repo “size” include all projects or just one? What about multiple branches? How much capacity is local storage?
A stock Unreal Engine project is several hundred gigs, consists of multiple solutions, multiple languages, and I would classify as large personally.
Without some kind of indexing it’s very awkward to work with and very slow. To work with LLMs and Unreal projects we create a local index, that index file alone is 46GB.
Without distributed compilers and caches it can take multiple hours to compile the main solution per platform (usually PC, Linux, Xbox, PlayStation, Switch, and sometimes mobile).
So the codebase easily fits on local storage so long as you don’t count assets (those are several TB) and extra so for source assets (10s of TB), and that’s per stream per large project.
Anyways, point is I disagree and think Unreal Engine is an example of large codebase that fits locally.
I won’t buy another Meta device. Bought the Quest 3 and now they keep installing games and apps on the device that I cannot remove to promote things. I don’t want any of that. Will most likely be replacing it with the Valve Deckard/Frame device as soon as possible.
We run a full Grafana stack (Loki, tempo, Prometheus, alloy agent, Grafana) and back out with self hosted S3 (we are all onprem physical hardware).
While I do like the stack we have, it is a lot of components to run and configure. Don’t think we have ever had any issues once it was up and running.
Does anyone have any thoughts about how this compares? We don’t have a huge amount of days, 1 month of metrics is about 200GB and logs isn’t a whole lot more, less than a TB I think for 2 weeks.
Do you have plans for mobile app? It looks really useful but the two places I would use it would both require I mobile app before I could switch to it.
It’s also important to note that the landing caused uneven crushing of the landing legs. The result being that the booster has a lean to it and they were unable to fully secure it with the octograbber. The leaning of the booster plus wind and rough seas was required to cause the failure. If the booster was level and fully secured it should have been fine.
The newer boosters have self levelling legs which remove the lean caused by uneven crushing of the landing leg cores.
Absolutely no offence at all! I tend to avoid Reddit these days and wanted to catch up on some SpaceX stuff. Avoiding Reddit means my main source of SpaceX news, a mix of r/SpaceX and r/SpaceXLounge, was something I was avoiding. Going back through Elon’s tweets seemed a decent way to catch up in a general sense. He seems to really like tweeting about SpaceX.
I learned through that attempt at going back through his tweets that, as you pointed out, Twitter is really not built for that. I guess I hadn’t really put much thought it in at the time, was just on my phone, curious about SpaceX, and thought it might be an OK way to get some updates.
https://epicgames.github.io/lore/explanation/system-design/#...