GZ — Gzipped Quantized GLB
The quantized GLB from this group as a deterministic gzip stream (no embedded filename, mtime 0) — what a CDN actually sends when a viewer advertises `Accept-Encoding: gzip`. It compresses to 55.6% of its source against 29.2% for the float32 twin, which is the point of shipping both: quantisation halves the file on disk and then gives most of that back over the wire.
gz
Single-file gzip (deflate) stream
- Contains
- quantized.glb
- Codec
- gzip (deflate)
- Uncompressed
- 48.9 KB
- Compressed
- 27.2 KB
A container-free gzip (deflate) stream — decompress it to recover quantized.glb. The bytes are the compressed data, so there is no inline content preview.
Specifications
- Codec
- gzip (deflate)
- Original Name
- quantized.glb
- Original Bytes
- 50092
- Gzip Level
- 9
- Mtime
- 0 (deterministic)
- Embedded Filename
- false
- Ratio Percent
- 55.6
- Sibling Ratio Percent
- 29.2
Testing contract
Expected to pass- Scenario
- Decompress and diff against quantized.glb, then compare the transferred size against the float32 twin's gzip.
- Expected result
- The stream decompresses byte-for-byte to quantized.glb and lands at 55.6% of it; measured over the wire the two twins are far closer than their uncompressed sizes suggest, so quantisation must be justified by GPU memory rather than by download size.
What is a .gz file?
GZ is a file compressed with gzip, using the DEFLATE algorithm within a simple single-stream container that stores one compressed file plus a small header and checksum. It compresses a single stream rather than bundling multiple files. It is ubiquitous for compressing logs, tarballs, and HTTP responses.
How to use this file
Use an example GZ to test gzip decompression, streaming inflate, checksum verification, and pipelines that transparently handle gzip-encoded content.
How to use this file for testing
“GZ — Gzipped Quantized GLB” is a deterministic Novus Examples fixture for Conversion testing, Performance testing. The same content exported across many formats and linked as a group, so you can convert one and diff against the expected twin.
Documented properties for this file: GZ · 27,873 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
3D and CAD fixtures carry one small, documented solid or scene. Convert and inspect against the known geometry, units, and structure; format twins let you diff interchange fidelity, and the 3D viewer previews the actual mesh.
Code examples
gunzip -k quantized.glb.gz # keep original
zcat quantized.glb.gz | headRelated files
- glbGLB — 64 Nodes Sharing One MeshAn 8x8 field of columns built from a single 12-triangle mesh referenced by 64 nodes with seeded random heights. Core-glTF instancing needs no extension: the file is tiny, and the interesting question is whether your renderer batches the 64 draws or issues them one by one.
- glbGLB — EXT_mesh_gpu_instancing (32 instances)Thirty-two copies of one cube expressed as instance attribute accessors on a single node under EXT_mesh_gpu_instancing — the extension that moves instancing off the scene graph and onto the GPU. A viewer without support shows exactly one cube at the origin, which is the tell.
- glbGLB — Interleaved Vertex Attributes (byteStride 32)Position, normal and UV packed into ONE bufferView with byteStride 32 and three accessors at offsets 0, 12 and 24 — the GPU-friendly layout, and the one a naive parser mis-reads because it assumes each accessor owns its view. Twinned here with a tightly-packed version of the same sphere.
- glbGLB — Tightly-packed Vertex AttributesThe same sphere with every attribute in its own bufferView and no byteStride — the layout most exporters emit and most parsers assume. The control against which the interleaved twin in this group is diffed.
- txtAllocation Profile — Folded Stacks Weighted in Bytes (txt)An allocation profile in the same folded syntax as the CPU profiles, but weighted in bytes rather than samples. The format carries no unit, so a viewer that assumes samples renders 65 MB of allocation as 68 million samples — which is what this fixture is for.
- txtHeap Profile — In-Use Bytes by Allocation Site (txt)A heap profile measuring bytes still live at the sample point, not bytes ever allocated — which is why its shape differs from the allocation profile of the same process. 620 MB retained across five sites, with an unbounded session cache at the top.
Generated by generation/models_p7.py. Free for any use, no attribution required — license.