Archive Qwen Turbo ten-image trial and measured seed-cache evidence

runs/3cc53336-2555-5e90-99c3-7b94dcb40acc/run.md

@@ -1,6 +1,6 @@
 # Images, music, and the limits of video on a 6 GB GTX 1060
 
-An older gaming GPU can still produce a useful library of images and short music clips. Video is a much harder proposition. Our October 2026 Packet Foundry tests on a Windows machine with a GTX 1060 6 GB produced 100 images in a planned prompt study, two music clips the user judged usable, and a collection of videos ranging from recognizable but flawed motion to complete colored noise. Every bad clip stays in the archive alongside the better ones.
+An older gaming GPU can still produce a useful library of images and short music clips. Our October 2026 Packet Foundry campaign on a Windows GTX 1060 with 6 GB VRAM now retains **133 generated files: 120 images, 11 videos and two music clips**, across **140 recorded attempts**. The images include the 100-request FLUX study, ten earlier checks and ten Qwen Image 2.1 Turbo follow-up images. The user judged both music samples usable; the videos range from recognizable but flawed motion to colored noise. Every poor output and all seven no-output failures remain in the archive.
 
 The most useful result is the range: roughly a minute for a 512-pixel image in the large FLUX.3 study, around eleven minutes for fifteen seconds of music, and anything from under two minutes to more than an hour for a short video. Those numbers describe these exact configurations and timing boundaries. They are not a general ranking of the models.
 
@@ -26,7 +26,7 @@ Briefs ranged from 16 to 463 words. Scenes included a fox crossing a creek, tea
 | 95th percentile | 99.69 s |
 | First request after the fresh process | 242.34 s |
 | Median of first seed variants | 74.03 s |
-| Median of immediately following variants | 39.40 s |
+| Median of next seed variants | 39.40 s |
 
 The paired speed difference has concrete cache evidence. Positive conditioning executed fifty times and was reused fifty times; negative conditioning executed once and was reused ninety-nine times. Sampling still ran for each changed seed. Fresh positive-conditioning intervals had an approximate 31.69-second median from recorded event boundaries. Calling every first image “cold” would obscure that most first variants reused an already running model while encoding a new brief.
 
@@ -46,6 +46,29 @@ Earlier fresh-prompt image pairs covered three generators. Their trace times sho
 
 These pairs retained the same Comfy process and loader state, with fresh conditioning and sampling on the second request. They used different architectures, step counts and settings, so this table is a record of tested configurations rather than an equal-quality speed contest. Earlier functionality checks, a delivery interruption and an explicit factory-restart recovery test are archived separately instead of being folded into clean pair statistics.
 
+## Generating several variations of one image brief
+
+A useful production workflow is to ask for five seed variations of one brief and choose the preferred image. Our actual evidence covers **two seed variants per brief**, not five, but it shows why keeping those requests together matters.
+
+The existing FLUX.3 study gives the stronger repeated evidence: all **50 second requests** reused both positive and negative text conditioning in the same runtime. Every paired graph differed only in sampler seed 42→43, the sampler ran again, and all 50 pairs produced different retained images. Excluding the initial-load pair, the other 49 pairs had a first/new-brief native median of **70.05s** and a following same-brief median of **38.49s**. The median within-pair saving was **32.12s**, with a median per-pair speed ratio of **1.85×**. Those are native server boundaries, separate from the Factory trace table above.
+
+| Measured FLUX.3 population | First/new-brief native median | Same-brief second native median |
+|---|---:|---:|
+| All 50 pairs | 71.67s | 38.40s |
+| 49 pairs excluding initial loading | 70.05s | 38.49s |
+
+The actual gap from first completion to the second start ranged from **10.422–31.712s**, with a **22.380s** median. These were consecutive requests with observed cache reuse, not zero-gap batch execution. The measured savings closely track the skipped positive encoding, but we did not randomize seed order or run a matched cache-disabled control. A copied encoder-probe duration on a cached request records its earlier encoding; it is not extra encoder work in the second request.
+
+### Qwen Image 2.1 Turbo: ten additional images
+
+We also tested the distinct `unsloth/Qwen-Image-2.1-Turbo-GGUF:Q4_K_M` checkpoint at 512×512, eight Euler steps and CFG1, using the exact official ManualSigmas schedule. All ten retained outputs passed the Foundry relay, independent PNG/checksum checks, actual LangSmith attachment retrieval and the native ten-case experiment check. Every original was also inspected visually; successful delivery does not remove material, geometry or prompt-adherence defects, which remain with each image in the gallery.
+
+Its first image took **320.246s native**, including loading and encoding. The next seed of the same brief took **95.234s** after an actual **34.322s** gap. Text encoding was cached; sampling and decoding executed again. This first-to-second difference combines initial/model-loading and encoding reuse; it does not isolate text-cache benefit alone. The eight following **new briefs**, still using the retained model runtime, had a native median of **199.712s**, range **194.865–223.135s**. Cached seed-variation time therefore must not stand in for fresh-brief latency.
+
+The practical arrangement is to keep a brief's complete composed prompt, input materials and relevant settings identical and send its seed variations consecutively to the same factory, profile and Comfy runtime. The cache belongs to that runtime; it does not travel inside a Foundry packet. Changing the prompt envelope, switching models or factories, restarting, or evicting cached state may remove the benefit. **No five-variation group or five-image completion time has been measured.** These FLUX and Qwen configurations also differ in architecture and step count; this is not an equal-quality speed comparison.
+
+[Browse the ten Turbo images](https://benchmarks.weeyuga.com/benchmarks/bd801c85.html) · [Read the sanitized pair evidence and cache findings](https://benchmarks.weeyuga.com/data/predator-media-20261021/seed-variant-cache-findings.json).
+
 ## Music: usable to the listener, expensive per second
 
 YuE2 INT8 ConvRot produced two fully decoded fifteen-second stereo FLAC files at 48 kHz. Factory traces took **700.26 and 634.17 seconds**, approximately 11 minutes 40 seconds and 10 minutes 34 seconds. The native graph durations were 696.921 and 630.994 seconds. Loader state remained available between requests; the second request changed the style wording and seed, so semantic generation and acoustic sampling both ran again.
@@ -93,4 +116,4 @@ Other retained records include the cancelled YuE2 CPU trial, Cog's initial atten
 
 For accepted outputs, the delivery checks verify checksums, full decoding, durable collection and acknowledgement. Saved LangSmith attachment bytes were independently decoded, and native experiment exports were checked where recorded. LangSmith's media-player UI was not separately inspected. The original noisy Cog videos passed file and delivery checks while failing visual usefulness: the separation is deliberate.
 
-The practical lesson from this machine is specific. A repeatable local image workload worked well enough to complete all one hundred planned requests. Two short music samples were usable to their listener, at a substantial time cost. Short video could complete, sometimes quickly, but our tested clips did not establish reliable requested motion. The published prompts, settings, poor outputs and failed attempts give the next builder something more actionable than a success headline.
+The practical lesson from this machine is specific. The FLUX study completed all 100 planned image requests, and the Qwen Turbo follow-up completed ten more; those subsets remain separate in the measurements. Two short music samples were usable to their listener, at a substantial time cost. Short video could complete, sometimes quickly, but our tested clips did not establish reliable requested motion. The published prompts, settings, poor outputs and failed attempts give the next builder something more actionable than a success headline.