DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to compress JSON event files smaller than zstd -3 with Glyd

Use the Glyd CLI to shrink a large JSON file and restore it exactly.

Who it is forA data engineer who stores large JSON event dumps and wants smaller files that still decompress to the original.

The problemLarge JSON event files take up storage and are slow to move, and the team wants a lossless format with faster reads.

The outcomeA .glyd file that is smaller than a zstd -3 copy and restores to the original JSON.

What you need first

  • Linux (x86_64 or aarch64) with an NVIDIA GPU: Ampere, Ada, Hopper or Blackwell, driver 580 or newer
  • For the Python and vLLM steps: Python with pip, and vLLM for serving
  • For the codec: Homebrew or a release tarball from the Glyd releases
  • A Glyd license from [email protected] if the work is commercial, since the README says commercial use needs one

Steps

  1. Install the CLI with brew install surya-koritala/glyd/glyd, or download a release tarball.
  2. Run glyd --max events.json -o events.glyd to compress the file.
  3. Run glyd -d events.glyd -o events.json to restore it.
  4. Compare the restored events.json with the original before deleting the source file.

Prompt for your agent

Using the repo surya-koritala/Glyd, install the glyd CLI and compress <input file> to <output file>.glyd with `glyd --max <input file> -o <output file>.glyd`. Restore it with `glyd -d <output file>.glyd -o <restored file>`, then report both file sizes and whether the restored file matches the original. Verify that the restored file is byte-identical to the input.

Caveat. The README's smaller-than-zstd claim comes from its own example, so test the size and speed on your own files before relying on it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page