Skip to main content

Loggetta

Plan the run. Train the model. Keep the evidence.

Loggetta checks your hardware, chooses a supported configuration for a Mixture-of-Experts (MoE) model, and runs QLoRA fine-tuning. It saves the plan and a JSON run report with memory use, timing, and checks that the selected optimizations actually ran. One install includes the runtime (experts4bit-qlora) and the GPU kernels (grouped-nf4-gemm).

Limits. Plans are estimates, not an out-of-memory guarantee. The released training path is single-GPU MoE training on Linux with a supported NVIDIA CUDA GPU. Dense models are planned but not yet supported for training. Dense training

pip install loggetta
loggetta inspect
loggetta plan Qwen/Qwen3-30B-A3B --seq 2048

The plan shows where weights will live, estimated memory use, and why alternatives were rejected. It checks the budget before downloading model weights. Estimates can miss; they are not an out-of-memory guarantee.

New in 0.5.0

  • Training plans no longer borrow another model's reserve. A model with no receipts on this GPU is priced at the card's worst measured training slack. In sample, no training plan now sits under its measured peak.
  • Plans record the backend switches their estimate read (with experts4bit-qlora 0.52.0 or later), and loggetta execute warns when the running process differs.
  • Dense plans: an estimate no longer falls when one of its terms rises.

Full list: CHANGELOG.

Train on your data

loggetta train Qwen/Qwen3-30B-A3B \
  --dataset ./data/train.jsonl --format text \
  --seq 512 --micro-batch 1 --steps 20 --seed 42 \
  --out runs/my-training --adapter-out adapters/my-adapter

Local JSONL, JSON, CSV, Parquet and TXT files, Hub datasets, Alpaca instructions and text-only chats are supported. Data is validated and tokenized before weights load. Chat data trains only the assistant turns by default. Reload the adapter with loggetta.load_adapter("adapters/my-adapter"). See the training guide.

To run a saved decision later: loggetta plan MODEL --out plan.json, then loggetta execute plan.json --out runs/. Pass earlier run reports back with --observations runs/ and later plans use those measurements.

Measured results

The included runtime and kernels do the compute; these are matched training runs, not planner benchmarks.

Workload Result
Qwen3-30B-A3B QLoRA · RTX 5090 Unsloth spends 1.92× e4b's GPU time per step, and 2.80× its wall-clock time on an AMD EPYC 7713 host. Comparable held-out loss; Unsloth peaked lower (24.27 vs 26.16 GB). Result
Why two numbers GPU time doesn't depend on the host. Unsloth runs about 14× e4b's CPU operations per step, so its wall-clock time grows on a slower host. Earlier wall-clock readings, before e4b's current defaults: 2.352× and 2.468×.
Planner memory check · Qwen3-30B-A3B · RTX 5090 24.54 GiB estimated process peak, 24.34 GiB measured, after calibration from earlier runs. One in-sample case, not a guarantee. In the MoE audit re-run with training plans no longer borrowing another model's reserve (evidence/2026-10-09-moe-plan-vs-driver-no-borrow), today's planner puts no RTX A2000 training plan under its measured peak, in sample (the replan section; older recorded plans were). Plan vs run · MoE audit

The comparison used torch 2.12.1+cu130 and transformers 5.5.0 for both frameworks, with matched adapters, initialization and tokens. Loggetta does not predict throughput.

Models

Model Tested in Loggetta
OLMoE-1B-7B-0924, Granite-3.1-3B-A800M training and serving run
Granite-4.0-H-tiny training run; serving refused (Mamba state)
Qwen3-30B-A3B, Qwen3.6-35B-A3B, ERNIE-4.5-21B-A3B planned; serving validated
LFM2-8B-A1B planned; serving refused (conv state)
Mixtral-8x7B-Instruct planned
Gemma-4-26B-A4B-it, Nemotron-3.5-Lightning-30B-A3B supported by the runtime; not yet in Loggetta's sweep

Every row is supported by the included runtime's QLoRA path. Hybrid models (Qwen3.6, Granite-4.0-H, LFM2, Nemotron-H) need --packing concat with chat or Alpaca data. The runtime's capability register is the authority.

Scope

Single-GPU MoE planning and QLoRA training; serving placement is planned, not launched. Not yet: multi-GPU, throughput prediction. GPU runs need Linux, an NVIDIA CUDA GPU and a compatible PyTorch. Pre-1.0.

Dense models are not supported for training yet: their plans are estimates that missed a held-out check (a further reading is pending), and their training runs only behind --allow-development-executor until a 24 GB capacity reading.

GitHub · Results · Architecture · Research and releases

Metadata

Release files for loggetta 0.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for loggetta 0.5.0
File Size Uploaded
loggetta-0.5.0.tar.gz 156.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for loggetta 0.5.0
File Interpreter ABI Platform
loggetta-0.5.0-py3-none-any.whl Python 3 none any Details

Total release size: 262.9 kB

Release files / loggetta-0.5.0.tar.gz

Download URL loggetta-0.5.0.tar.gz
Size 156.8 kB
Tags Source
SHA-256 checksum
How to use checksums
035a9120235853c5710c8b6871fa60af398d8a263280570c6c7acad1c46a2a33
BLAKE2b-256 checksum
How to use checksums
7b7242d201d9bd3d0874d5c45f0e77ad485487cf1fa4b4f60482eb3a75191a7d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.

Transparency log

Release files / loggetta-0.5.0-py3-none-any.whl

Download URL loggetta-0.5.0-py3-none-any.whl
Size 106.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b72629d2243ca81190696148b54a5ffd337f991f92a92375c7376207c646e4c4
BLAKE2b-256 checksum
How to use checksums
5d22923c95c53ebe2d22787d1b0a2c87ec80eaeb5aba8286e35b8f4ebbdaf2e4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.

Transparency log

Release history Release notifications | RSS feed

0.6.0

2 release files

This release

0.5.0 This release

2 release files

0.4.0

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

0.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page