Play the video (opens in a new tab)Video on YouTube by vogel
- Views
- 66,786
- Duration
- 4:07
Read from YouTube on . Counts change daily.
Reported by the author
- Avg response time
- ~200 ms
with average response times around 200 milliseconds
youtube.com - Speed claim tested
- ~200x
TypeSafe reports roughly 200× faster performance on its workflow benchmarks
youtube.com
Vogel runs Jev over their own inbox. They exported 1,500 emails and asked four questions about each: category, priority, whether it is spam, and whether it needs a reply. The first batch of 100 ran with eight parallel workers. They report an average of 200 ms per email, a p95 (the time 95% of requests finish within) of 240 ms, and about 38 emails a second. Vogel spot-checks a few results on screen: an OpenAI account notice and a domain revocation marked high priority, and a reply-needed probability of 91% on an account violation email.
A second run of 1,000 emails stays around 200 ms per email and passes 1.1 million input tokens while it runs. The usage page shows 5 cents spent. Vogel notes it is a shared team account, so that figure also covers other people’s playground calls. The latency shown is the full round trip, from sending the email to getting the answer back.


