CompactGUI VS tikv

CompactGUI

Also, check out CompactGUI. It's a more user-friendly and efficient way of using Windows' built-in compression to cut the game's file size almost in half. It makes load times marginally longer (like 5-10%) and needs to be redone every few updates to keep the size down, but it works.

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.

You can also just use compactGui smaller filesizes without having to remove dialogs or cutscenes or anything. Obviously how much space is regained depends on how well it was compressed originally. With triple A titles perhaps getting 10% back, while things like ark can literally be shrunk by hundreds of gigs.

Not really related to your question but if you want to try and save some space you can give this a go, I've used it before and never had any issues. https://github.com/IridiumIO/CompactGUI

Meet you new best friend. https://github.com/IridiumIO/CompactGUI

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.