Usage

Because Loca runs real models on real hardware, it is worth being able to see what it is using. The Usage group is that window: it shows what is running and how much space Loca is taking up, split between this device and the Core, so you can tell where the work and the gigabytes are actually going.

Services and storage

Each side is reported two ways. Services lists the moving parts that are running right now, the language model, speech, and the rest, with what each is costing in processor and RAM, so a slow reply or a warm fan has an explanation you can point to. Storage accounts for what Loca keeps on disk: your sessions and memories, the models you have downloaded, and the rest of its state. Models are usually the bulk of it, which is the figure to check when you are deciding whether to clear space.

When the Core runs on another machine, splitting the two matters: the device side is your laptop, while the Core side is wherever the heavy work is really happening. Seeing both at once is how you tell a busy Core from a busy Client.

How It Works

Nothing here is stored or configured; the group is a live readout, which is why it has no settings to change. For Services, Loca asks the operating system about each of its running parts by process and reads back the processor and memory each is using at that moment, the same numbers a system monitor would show, attributed to the specific piece of Loca responsible. For Storage, it walks the folders under ~/.loca and adds up what it finds, grouping the total into the categories you see. Both are measured on demand when you open the group, so the figures are a snapshot of right now rather than a running tally Loca has to keep.

Next, how Loca keeps itself current and how to run more than one build at once: Updates and Channels.