67 lines
2.1 KiB
Markdown
67 lines
2.1 KiB
Markdown
# Optimized Workflows
|
|
|
|
This section is the maintained layer for "best current" master workflows.
|
|
|
|
The `models/` tree stores collected originals and community finds.
|
|
|
|
The `optimized/` tree stores the cleaned-up workflows built from analyzing what we have collected.
|
|
|
|
The `optimized/notes/` tree stores accumulated optimization notes so future review passes can reuse prior judgments instead of re-reading every collected workflow from scratch.
|
|
|
|
## Purpose
|
|
|
|
These workflows are intended to become the practical default choices for each category after comparing:
|
|
|
|
- official workflows
|
|
- community workflows
|
|
- custom-node variants
|
|
- model-specific optimizations
|
|
- quality vs speed tradeoffs
|
|
|
|
## Categories
|
|
|
|
- `text-to-image/`
|
|
- `image-edit/`
|
|
- `image-to-video/`
|
|
- `text-to-video/`
|
|
- `upscale-restoration/`
|
|
|
|
## Current best-current masters
|
|
|
|
- `text-to-image/zimage-turbo-3070-fast-start/`
|
|
- `image-edit/zimage-turbo-3070-inpaint-start/`
|
|
- `image-edit/flux2klein-9b-fp8-edit-master/`
|
|
- `image-to-video/ltx23-3070-simple-master/`
|
|
- `text-to-video/minimax-h3-3070-turbo-master/`
|
|
|
|
## Workflow format
|
|
|
|
Each optimized workflow should have its own folder and usually include:
|
|
|
|
- `workflow.json` or another portable Comfy workflow asset
|
|
- `README.md` with a compact record of the parameters and graph changes that define the current master
|
|
- optional notes, screenshots, or benchmark artifacts
|
|
|
|
## Notes layer
|
|
|
|
Use `optimized/notes/` for durable working notes such as:
|
|
|
|
- category heuristics
|
|
- strong and weak source workflows
|
|
- recurring node/version pitfalls
|
|
- preferred model paths
|
|
- unresolved test questions
|
|
- "best current" assumptions waiting for proof
|
|
|
|
## Update policy
|
|
|
|
This section is reviewed on a Sunday-evening cadence.
|
|
|
|
The weekly review should:
|
|
|
|
- inspect newly collected workflows
|
|
- decide whether a category master should be created or updated
|
|
- document what changed and why
|
|
- document the workflow settings that actually changed, especially prompt, negative prompt, CFG, steps, sampler, scheduler, seed, denoise, resolution, model swaps, LoRA weights, ControlNet wiring, and any node removals or additions
|
|
- commit and push changes before reporting back
|