oxigraph-optimize(1)

πŸ“¦
version 0.5.10 Β· 2 versions
, in nixos 26.05, nixpkgs unstable, ubuntu resolute, ubuntu stonking

✨ oxigraph-optimize β€” the manual page bestie πŸ’–

okay so welcome to the oxigraph-optimize(1) glow-up, part of the General Commands Manual family. this is the page about the lil command that optimizes your database storage. it's giving ✨maintenance era✨. let's get into it 🫢


🌸 NAME 🌸

oxigraph-optimize β€” bestie, it optimizes the database storage. that's the whole vibe. πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

oxigraph optimize <-l|--location> [-h|--help]

πŸ¦‹ DESCRIPTION πŸ¦‹

so. this command optimizes the database storage. literally that's the job, and it does it well. πŸ‘‘

here's the tea tho πŸ“ β€” this optimization is already done by default in the background when serving requests. so it's probably not useful in most cases, ngl. it's lowkey the "you don't need this" of commands.

the one exception? if you provide a read-only SPARQL endpoint under heavy load β€” then yeah, this is your moment, and it's iconic. 🌈

no cap: for like 99% of you this is a vibe check you can skip. but if that read-only + heavy load situation is you? go off. πŸ”₯

✨ OPTIONS ✨

  • -l, --location <LOCATION> β€” the directory where Oxigraph data are persisted. your data lives here, so point it at the right place, bestie. 🏠
  • -h, --help β€” print help. (and heads up: for a summary you can peek at '-h', iykyk.) πŸ“–

πŸ’œ that's it, that's the page πŸ’œ

short and sweet, fr fr. this page comes to you from optimize (the source) and oxigraph-optimize(1) β€” aka the manual page name β€” and honestly? she ate. periodt. πŸ’…βœ¨

πŸ“¦ where this page comes from