Archive ten matched Qwen Turbo Q8 outputs and Q4 comparison 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. 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.
+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 **143 generated files: 130 images, 11 videos and two music clips**, across **150 recorded attempts**. The images include the 100-request FLUX study, ten earlier checks, ten Qwen Turbo Q4 follow-up images and ten matched Q8 comparison outputs. The user judged both music samples usable; 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.
 
@@ -69,6 +69,45 @@ The practical arrangement is to keep a brief's complete composed prompt, input m
 
 [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).
 
+### Qwen Turbo Q4 and Q8: the same ten briefs and seeds
+
+Ten further Q8_0 outputs reuse the exact ten Q4 prompts, seeds 42–51, order and eight-step Euler/CFG1 ManualSigmas settings. The earlier Q4 originals remain unchanged. Only the generator file and output prefix differ in the executed graphs; both sets retain the same CPU INT8 encoder, CPU VAE and FP32 runtime settings. All ten Q8 results passed actual relay/acknowledgement, full decoding/checksums, output-attachment retrieval and paired native ten-case LangSmith experiment checks. Both sets of originals were inspected visually, with defects retained beside each output.
+
+| Matched workload | Q4 native time | Q8 native time |
+|---|---:|---:|
+| Initial request; actual inherited loading/cache context | 320.246s | 541.410s |
+| Same first brief, next seed | 95.234s | 93.391s |
+| Eight subsequent new briefs, retained-runtime median | 199.712s | 446.477s |
+
+The Q8 same-brief follow-up started 24.958s after its predecessor finished; its native encoder-cached flag was `true`. These are whole native graph times; Factory traces have separate boundaries. The first Q8 request inherits the existing Comfy/runtime state, so its loading and text-cache history need not match the earlier Q4 first request. Offloading, cache, initialization and other device workloads remain possible timing confounders.
+
+During case 5, the local status coordinator stopped after three connection errors while the native generation continued and completed successfully. Warehouse and native-history readbacks confirmed one successful attempt. The unchanged finite coordinator collected that saved result before submitting case 6, preserving the same factory runtime. The actual case 5-to-case 6 native idle gap was 890.033s; every inter-run gap is retained in the comparison data. This monitoring interruption created no additional generation attempt or failed-generation record.
+
+Fresh-prompt CPU encoding was slower in this Q8 series. The earlier Q4 fresh-brief encoding intervals ranged from 100.109 to 115.984s; the Q8 range was 119.328 to 457.125s. The eight new briefs give these observer-interval medians:
+
+| Observed phase, eight new briefs | Q4 median | Q8 median |
+|---|---:|---:|
+| CPU text encoding | 103.109s | 247.344s |
+| Sampling, including loading | 68.703s | 108.328s |
+| VAE decoding | 28.329s | 50.414s |
+
+These intervals include preparation/loading and observer delivery overhead. They locate the extra elapsed time without establishing its cause. A Q8 snapshot recorded many total memory faults but few hard page inputs; it does not establish disk paging as the bottleneck. Windows `PagefileUsage`/`PrivateUsage` counters mean private commit charge, rather than measured disk-pagefile residency. See [Microsoft's process-memory counter definitions](https://learn.microsoft.com/en-us/windows/win32/api/psapi/ns-psapi-process_memory_counters_ex) and [working-set/fault definitions](https://learn.microsoft.com/en-us/windows/win32/memory/working-set).
+
+Q8 stores more weight precision, but it is not automatically a prettier image. Q4 is not a high-precision ground truth, and no aesthetic score or whole-VRAM residency claim follows from the comparison. The Q8 packed file alone is 7.12 GiB, before live working memory. This is still two seed variants for the first brief, not a measured five-image batch. Per-case material, geometry, text and prompt-adherence findings remain visible for both quants.
+
+Smaller generator files are available at the same pinned Unsloth revision. We inspected their published metadata; none of these Q2/Q3 variants was generated in this comparison:
+
+| Available generator quant | Packed file size, decimal GB |
+|---|---:|
+| [Q2_K](https://huggingface.co/unsloth/Qwen-Image-2.1-Turbo-GGUF/blob/5d1f9f759ea877ae556cda88dbec958b62ad3809/qwen-image-2.1-turbo-Q2_K.gguf) | 2.47 GB |
+| [Q3_K_S](https://huggingface.co/unsloth/Qwen-Image-2.1-Turbo-GGUF/blob/5d1f9f759ea877ae556cda88dbec958b62ad3809/qwen-image-2.1-turbo-Q3_K_S.gguf) | 2.72 GB |
+| [Q3_K_M](https://huggingface.co/unsloth/Qwen-Image-2.1-Turbo-GGUF/blob/5d1f9f759ea877ae556cda88dbec958b62ad3809/qwen-image-2.1-turbo-Q3_K_M.gguf) | 3.17 GB |
+| [Q3_K_XL](https://huggingface.co/unsloth/Qwen-Image-2.1-Turbo-GGUF/blob/5d1f9f759ea877ae556cda88dbec958b62ad3809/qwen-image-2.1-turbo-Q3_K_XL.gguf) | 3.61 GB |
+
+File size leaves out dequantization buffers, compute workspaces, activations, encoder/VAE and other GPU use. A smaller packed file is a candidate for a future residency test, not proof that its entire active stage fits a 6 GB GPU.
+
+[Compare all ten Q4/Q8 image pairs](https://benchmarks.weeyuga.com/benchmarks/ef874435.html) · [Download exact matched timings, cache context and pair mapping](https://benchmarks.weeyuga.com/data/predator-media-20261021/qwen-turbo-q4-q8-comparison.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.
@@ -116,4 +155,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. 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.
+The practical lesson from this machine is specific. The FLUX study completed all 100 planned images, the Qwen Turbo Q4 follow-up completed ten, and the matched Q8 comparison added ten further outputs; each measured subset remains separate. 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.