Compactor VS tikv

You can already do the very basic version of that by using Compactor. Essentially it uses Windows 10's compression algorithms to make your games smaller. A lot of variance between games based on what their files consist of, but I generally get ~25% more space on my drives. Of course, a single update to the game might mean that you have to pack them again, but it's still a pretty good upside with practically no performance loss.

This will also help.

ARK practically needs its own 500GB SSD, specially if you start installing mods on top of having all of the DLCs. However, it's possible to bring down its size massively if you use this software, it works exceptionally well in ARK, being able to reduce it to about half its size. For example, my ARK installation went from like 320 GB to 175 I believe, which is still huge, but only about as much as any modern AAA game.

You can chuck compact.exe at it by hand (use the /exe option), or if you'd prefer to avoid the command line there's my Compactor tool, or the venerable CompactGUI.

They actually don't compress it. Using a simple compressor like this one for instance, the size decreases by half, if not a bit more than it. Tested it with the base game and it went from 200GB to 100GB.

I should press on and finish my Compactor rewrite, I guess.

7zip, microsoft powertoys (useful utilities n stuff), hyper-v (VM stuff), OBS, optimizer (https://github.com/hellzerg/optimizer) (privacy stuff + system tweaks), compactor (https://github.com/Freaky/Compactor) (uses windows compact.exe and provides a GUI for a otherwise cmd based tool) also qbittorrent

I know that very similar functionality to this is in TiDB Serverless ( https://tidbcloud.com ). TiDB is a distributed relational database. It uses TiKV ( which is a key/value engine ) as the storage engine. You could use SQL to access your K/V records. There is ongoing work in TiKV to support S3 directly as the storage backend ( https://github.com/tikv/tikv/issues/6506 ) .

TiKV is basically a layer on top of rocksdb https://github.com/tikv/tikv/blob/956610725039835557e7516828...

> Many,many smart people…

If you look inside the code you can see the stated features are a result of underlying engine (TiKV [0] also in c and rust from pingcap). Surrealdb is standing on shoulders of giants at present, they are TiKV, FoundationDB and rocksdb. The feature set they mentioned mostly coming from TiKV at present.

[0] https://tikv.org/

Hi Diggsey, great question. We are currently focussed on functionality and stability, and then will draw our attention to performance. Coming this week we have a RocksDB storage implementation. We've only just launched our initial beta version, and we know there is a lot of improvement and work to be done (some of these performance issues we know about already and are on our Github issues list).

With regards to the consistency/isolation model, SurrealDB sits on top of a number of key-value stores. By using the distributed highly-available TiKV storage backend, https://tikv.org, (and we have a FoundationDB integration in the works), the database is designed to be highly-scalable and highly-available. The same guarantees (albeit just single-node, so no high-availability or scalability) will be available with the RocksDB implementation coming this week. By sitting on top of these key-value stores, SurrealDB ensures that all transactions are ACID compliant. We don't want to go for speed (for instance by writing to /dev/null) over anything, but want SurrealDB to be a reliable and performant backend for any application. Obviously we have a way to go to catch up with PostgreSQL (launched in 1996), but we will strive to get there!

If you are looking for a production ready distributed store written in Rust. Check out TiKV(https://github.com/tikv/tikv), which was also mentioned in the acknowledge section of the project's README.

There's also a full-featured distributed RDBMS called TiDB built on top of TiKV.