Brooooooklyn commited on
Commit
15aac65
·
verified ·
1 Parent(s): a0749ee

Add model card

Browse files
Files changed (1) hide show
  1. README.md +10 -10
README.md CHANGED
@@ -38,20 +38,20 @@ model_type: qwen3_5_moe
38
 
39
  | Repo | Format | Size | Decode (tok/s) |
40
  |---|---|---|---|
41
- | [Brooooooklyn/Ornith-1.0-35B-UD-Q3_K_XL-mlx](https://huggingface.co/Brooooooklyn/Ornith-1.0-35B-UD-Q3_K_XL-mlx) | UD-Q3_K_XL | 17 GB | 103.8 |
42
- | [Brooooooklyn/Ornith-1.0-35B-mxfp4-mlx](https://huggingface.co/Brooooooklyn/Ornith-1.0-35B-mxfp4-mlx) | MXFP4 | 20 GB | 90.1 |
43
- | [Brooooooklyn/Ornith-1.0-35B-UD-Q4_K_XL-mlx](https://huggingface.co/Brooooooklyn/Ornith-1.0-35B-UD-Q4_K_XL-mlx) | UD-Q4_K_XL | 22 GB | 87.0 |
44
- | [Brooooooklyn/Ornith-1.0-35B-nvfp4-mlx](https://huggingface.co/Brooooooklyn/Ornith-1.0-35B-nvfp4-mlx) | NVFP4 | 23 GB | 87.8 |
45
- | **[Brooooooklyn/Ornith-1.0-35B-UD-Q5_K_XL-mlx](https://huggingface.co/Brooooooklyn/Ornith-1.0-35B-UD-Q5_K_XL-mlx) (this model)** | **UD-Q5_K_XL** | **26 GB** | **91.2** |
46
- | [Brooooooklyn/Ornith-1.0-35B-UD-Q6_K_XL-mlx](https://huggingface.co/Brooooooklyn/Ornith-1.0-35B-UD-Q6_K_XL-mlx) | UD-Q6_K_XL | 31 GB | 87.1 |
47
- | [Brooooooklyn/Ornith-1.0-35B-UD-Q8_K_XL-mlx](https://huggingface.co/Brooooooklyn/Ornith-1.0-35B-UD-Q8_K_XL-mlx) | UD-Q8_K_XL | 36 GB | 84.2 |
48
- | [Brooooooklyn/Ornith-1.0-35B-mxfp8-mlx](https://huggingface.co/Brooooooklyn/Ornith-1.0-35B-mxfp8-mlx) | MXFP8 | 36 GB | 80.0 |
49
 
50
- Benchmarked on a **cool Apple M5 Max**: median decode throughput over three 512-token generations, with a 3-minute idle cooldown before each model. (Sustained decode on Apple Silicon is thermally sensitive — back-to-back benchmarking on a hot chip can understate throughput by 20–30%, so every model here was measured from a comparable cool start.)
51
 
52
  ## Performance
53
 
54
- Steady-state decode: **91.2 tok/s** (**1.6x** vs BF16) on Apple M5 Max. Decode is memory-bandwidth bound on Apple Silicon — fewer bytes per token directly translates to higher throughput. The MoE architecture activates only 8 of 256 experts per token (~3B active out of 35.9B total), so the active-weight footprint streamed per token is what matters.
55
 
56
  ## Output Quality
57
 
 
38
 
39
  | Repo | Format | Size | Decode (tok/s) |
40
  |---|---|---|---|
41
+ | [Brooooooklyn/Ornith-1.0-35B-UD-Q3_K_XL-mlx](https://huggingface.co/Brooooooklyn/Ornith-1.0-35B-UD-Q3_K_XL-mlx) | UD-Q3_K_XL | 17 GB | 111.6 |
42
+ | [Brooooooklyn/Ornith-1.0-35B-mxfp4-mlx](https://huggingface.co/Brooooooklyn/Ornith-1.0-35B-mxfp4-mlx) | MXFP4 | 20 GB | 107.8 |
43
+ | [Brooooooklyn/Ornith-1.0-35B-UD-Q4_K_XL-mlx](https://huggingface.co/Brooooooklyn/Ornith-1.0-35B-UD-Q4_K_XL-mlx) | UD-Q4_K_XL | 22 GB | 102.3 |
44
+ | [Brooooooklyn/Ornith-1.0-35B-nvfp4-mlx](https://huggingface.co/Brooooooklyn/Ornith-1.0-35B-nvfp4-mlx) | NVFP4 | 23 GB | 94.6 |
45
+ | **[Brooooooklyn/Ornith-1.0-35B-UD-Q5_K_XL-mlx](https://huggingface.co/Brooooooklyn/Ornith-1.0-35B-UD-Q5_K_XL-mlx) (this model)** | **UD-Q5_K_XL** | **26 GB** | **95.4** |
46
+ | [Brooooooklyn/Ornith-1.0-35B-UD-Q6_K_XL-mlx](https://huggingface.co/Brooooooklyn/Ornith-1.0-35B-UD-Q6_K_XL-mlx) | UD-Q6_K_XL | 31 GB | 93.1 |
47
+ | [Brooooooklyn/Ornith-1.0-35B-UD-Q8_K_XL-mlx](https://huggingface.co/Brooooooklyn/Ornith-1.0-35B-UD-Q8_K_XL-mlx) | UD-Q8_K_XL | 36 GB | 91.5 |
48
+ | [Brooooooklyn/Ornith-1.0-35B-mxfp8-mlx](https://huggingface.co/Brooooooklyn/Ornith-1.0-35B-mxfp8-mlx) | MXFP8 | 36 GB | 84.8 |
49
 
50
+ Benchmarked on a **cool Apple M5 Max**: median decode throughput over three 512-token generations, with a 60-second idle GPU cooldown after every generation. (Sustained decode on Apple Silicon is thermally sensitive — back-to-back benchmarking on a hot chip can understate throughput by 20–30%, so every model here was measured from a comparable cool start.)
51
 
52
  ## Performance
53
 
54
+ Steady-state decode: **95.4 tok/s** (**1.5x** vs BF16) on Apple M5 Max. Decode is memory-bandwidth bound on Apple Silicon — fewer bytes per token directly translates to higher throughput. The MoE architecture activates only 8 of 256 experts per token (~3B active out of 35.9B total), so the active-weight footprint streamed per token is what matters.
55
 
56
  ## Output Quality
57