It's good looking, and I liked it. The trial page accessed from the hugging face website is a very inefficient experience when I use Mozilla and the dark theme, FYI.
lnenad
Very nice! Thank you for building this.
rambambram
Leeches.
esafak
Why does the 'Quality vs Cost of Web Content Extraction' chart not have zero cost at the origin? Up to the right does not have to mean better; we can read.
show comments
rishav2580
ongrats on the release! The architectural insight to switch from a bandwidth-bound decoder (token-by-token generation) to a compute-bound encoder (single forward pass over 8k chunks) is brilliant—the 20x speedup and cost drop from $159k to $7.9k per billion pages is massive for web-scale pipelines.
As someone building AI developer utilities and document tools, I have two quick technical questions:
How well does the <|sep|> block-marker architecture handle heavily obfuscated HTML or adversarial SEO spam where boilerplate is styled to look like semantic body text?
Have you tested running pulpie-orange-small (210M) quantized (e.g., INT8/FP8) on consumer edge GPUs or CPU-only setups for local RAG pipelines?
Amazing work on open-sourcing the teacher and distilled weights on Hugging Face!
It's good looking, and I liked it. The trial page accessed from the hugging face website is a very inefficient experience when I use Mozilla and the dark theme, FYI.
Very nice! Thank you for building this.
Leeches.
Why does the 'Quality vs Cost of Web Content Extraction' chart not have zero cost at the origin? Up to the right does not have to mean better; we can read.
ongrats on the release! The architectural insight to switch from a bandwidth-bound decoder (token-by-token generation) to a compute-bound encoder (single forward pass over 8k chunks) is brilliant—the 20x speedup and cost drop from $159k to $7.9k per billion pages is massive for web-scale pipelines.
As someone building AI developer utilities and document tools, I have two quick technical questions:
How well does the <|sep|> block-marker architecture handle heavily obfuscated HTML or adversarial SEO spam where boilerplate is styled to look like semantic body text? Have you tested running pulpie-orange-small (210M) quantized (e.g., INT8/FP8) on consumer edge GPUs or CPU-only setups for local RAG pipelines? Amazing work on open-sourcing the teacher and distilled weights on Hugging Face!