Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 34 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -754,6 +754,28 @@ being followed. The two archive rows the report prints are tagged
`note: can be downloaded again; safe to remove`, so it is visible which rows
`remove-downloads` acts on.

The report also lists `Engine installs`: each Lemonade copy on disk and its
size. Lemonade installs into the active ROCm runtime's own folder when one is
active and into the data folder otherwise, so a machine that installed
Lemonade before its first SDK can hold two full copies (about 25 GiB each). The
copy Lemonade runs from is `in use`. A copy it is not using right now is marked
`not used right now`, which is not a promise it stays unused: Lemonade installs
into the active ROCm runtime's folder, so a copy inside a ROCm install is reused
as soon as that install becomes active, and is never marked reclaimable. Only
the data folder's copy, which no ROCm install owns, is marked reclaimable, and
nothing removes it automatically: delete its `runtime`, `downloads` and `extract`
folders to free the space. A copy is only called unused when Lemonade's install
record points at another copy that is really there: if the record names a folder
with no install, or cannot be read, the report says so and marks no copy
reclaimable. A copy inside a runtime folder
also counts toward that runtime's size. `rocm runtimes uninstall` removes it
with the runtime and clears Lemonade's install record, so Lemonade is no longer
recorded as installed; it says so when the record could not be cleared, and when
it could not be read it names `rocm engines install lemonade`, which rewrites
the record and keeps a current install.
For an external or imported runtime, uninstall only unregisters it, so its
Lemonade copy stays and the report does not say otherwise.

The report also lists `local server records`: one JSON record plus the engine's
log for each `rocm serve --managed` launch, kept after the server stops.
`rocm services list --all` lists them, and no `rocm storage` command removes
Expand Down Expand Up @@ -783,6 +805,18 @@ and installs once more; see
[Lemonade backend alignment](https://github.com/ROCm/rocm-cli/blob/main/docs/engine-plugins.md#lemonade-backend-alignment-on-engine-install) for the details and for
`ROCM_CLI_DISABLE_LEMONADE_BACKEND_ALIGNMENT`, which turns both off.

Before Lemonade writes a new install, whether from `rocm engines install
lemonade` or the first `rocm serve` that needs it, it prints the folder it is
installing into, the download (up to about 4.4 GiB) and disk use (up to about
25 GiB) of its llama.cpp ROCm backend, and any Lemonade install it is not
reusing. Those are upper bounds: Lemonade picks the backend after the install
starts, and a smaller one needs less. So it stops before downloading only when
the drive cannot hold Lemonade itself (about 16 MiB), and with less room than
the ROCm backend or the finished install it warns and continues. An install that
replaces the existing one (`--reinstall`, or a new Lemonade version) deletes it
first, so its space counts as free and the notice says so. On Windows the
backend download's own progress appears in the console.

`--yes` approves the system-package installs vLLM needs (OpenMPI, libatomic and
libnuma), including a `sudo` password prompt. `engines install` never asks for
confirmation. Without `--yes`, a Linux host with root or passwordless `sudo`
Expand Down
Loading
Loading