开放杰夫
OpenJev

原始链接: https://openjev.com/

**OpenJev** 是一款基于浏览器的实验性工具,旨在对从本地大语言模型(LLM)提取决策概率的两种方法进行基准测试。 该平台允许用户比较: 1. **直接读取(Direct Readout):** 直接从模型的内部 Logits 中提取选择概率,无需解码文本。 2. **生成(Generation):** 强制模型以 JSON 文本格式逐个 token 输出概率分布。 所有流程均在浏览器中利用本地 GPU 运行;没有任何数据会被发送至后端。用户可以选择各种模型尺寸(从 0.6B 的 Qwen3 到 4B 的 Qwen3.5),以观察在速度和延迟方面的性能差异。 由于模型使用量化后的 GGUF 权重在浏览器中运行,因此计时指标提供了关于不同架构如何处理推理的真实视角。该实验突显了直接、高效的计算与资源密集型、分步文本生成方法之间的权衡。无需排队等待——只需选择一个模型,将其加载到缓存中,即可自行比较执行时间。

最近的一场 Hacker News 讨论聚焦于“OpenJev”的发布,这是一个试图利用小型大语言模型(LLM)来模拟 Jev AI 模型决策行为的开源项目。 社区反应褒贬不一。一些用户称赞 Jev 框架独特且高精度的方法,认为它有潜力发展成为一种对现实决策非常有用的工具。另一些用户则对命名表示困惑和怀疑,指出该项目与原 Jev 团队并无关联,可能会产生误导。 技术层面的批评主要集中在工具的性能和方法论上。参与者质疑该模型的评分逻辑,特别是为何它强迫用户在选项间做出偏好选择,而非允许存在不确定性;此外,还有人质疑其底层架构与标准仅编码器(encoder-only)模型相比是否有显著差异。另外,有一位用户指出,尽管该工具比标准大语言模型更快,但仍存在延迟。 总的来说,这场讨论凸显了人们对这些技术所呈现的“杰文斯悖论”(Jevons Paradox)特性的普遍兴奋——即效率的提升催生了大量新的应用场景——同时也提出了关于知识产权以及大语言模型被广泛用于网页设计这一趋势的疑问。
相关文章

原文
openjev

A live, local experiment

A local model can either read probabilities for your allowed options without decoding them, or write the same kind of distribution token by token. Pick a size, run both on your own GPU, and measure the difference.

browser onlyno backendyour timings1.56 GB model

There is no waitlist! Just try it out ↓

MiniCPM5 2B is selected by default. On a phone or smaller device, switch to Qwen3 0.6B in the model box if needed.

00 / setup

Load the model once

Larger model. Loading may be slower or may not fit on some low-end devices.

Model performancehigher is better

Native BF16 · TypeSafe: same 102-row subset · Jev: published result · browser builds are quantized

download / cachestarts only when you click load

model loaddownload and prepare

warmupcompile passes for both methods

Weights come from Hugging Face and remain in your browser cache. Inputs never leave this page. First load can take several minutes depending on the selected model, network and GPU.

01 / decision

Give it a real choice

Try an example

Both paths receive the same decision. One reads option probabilities directly; the other asks the model to write its option probabilities as JSON text.

your decisionstate + question + options

same local modelMiniCPM5 · 2B


read logitsA…T probabilities

write tokens{options + probabilities}

02A / direct readout

Choice probabilities

no decoding

Read the model’s choice logits and normalize only across the options you supplied.

waiting for a run

total

input

output
1 readout

02B / generation

JSON probabilities

token by token

Ask the model to estimate the same displayed-option distribution and write it as JSON. Watch every token arrive.

waiting for a run

first token

total

input

output

measured wall-time ratiorun it on your GPU

The methods run sequentially on the same loaded model so they do not contend for one GPU. Direct runs first, then generation.

What these numbers do—and do not—mean

Conditional probabilities. Direct scores are a softmax over only the displayed option tokens. They are not calibrated confidence and do not include every answer the model might prefer.

Local model tiers. The phone model trades accuracy for size. MiniCPM is the desktop default. The 4B option needs substantially more memory. None is claimed to match Jev.

Real local timing. Setup, warmup, prompt preparation, direct execution, first generated token and generation completion are timed with performance.now(). No canned results appear.

Quantized weights. The demo uses pinned GGUF builds through wllama. Quantization can change both quality and speed.

联系我们 contact @ memedata.com