正在加载视频...

视频加载失败

We’re launching Optima. Now anyone can create a custom benchmark for their use case, leveraging Artificial Analysis’ leading research and platform Building and running benchmarks is difficult. We have distilled Artificial Analysis’ research and experience developing benchmarks into Optima, a new platform for benchmarking models on your own workloads...

133,952 次观看 • 3 个月前 •via X (Twitter)

32 条评论

Artificial Analysis 的头像
Artificial Analysis3 个月前

Build and run your own benchmark today:

Chris 🇨🇦 的头像
Chris 🇨🇦3 个月前

🐐🐐🐐

Command Code 的头像
Command Code3 个月前

Congrats y'all!!

Jeet Jain 的头像
Jeet Jain3 个月前

Woah, this is actually useful, though a very niche case, but can be a better reporting of actual results, on someone's personal use case

Kol Tregaskes 的头像
Kol Tregaskes3 个月前

Well this could be good timing. 👀

Perceptron.cloud 的头像
Perceptron.cloud3 个月前

Way to go 🚀

Hermann Saah 的头像
Hermann Saah3 个月前

That's great 👍🏽

Inflectiv AI ⧉ 的头像
Inflectiv AI ⧉3 个月前

Adding cost and latency makes model evaluation far more practical for production teams. The best model is not always the highest-scoring one.

Asharib Ali 的头像
Asharib Ali3 个月前

one of the best product for enterprise to find-out the right ai system for their use-cases, cool stuff ❤️

Jacob Beers 的头像
Jacob Beers3 个月前

Another fantastic idea. You guys are absolutely killing adding practical and useful features to AA.

agenttrader 的头像
agenttrader3 个月前

@_micah_h Smart. A lot of companies are missing the bigger picture

Branding Waves 的头像
Branding Waves3 个月前

Benchmarking your own workload is far more useful than generic scores.

Sebastian Buzdugan 的头像
Sebastian Buzdugan3 个月前

i've seen custom benchmarks become training sets within weeks, how does optima detect leakage

Josh 的头像
Josh3 个月前

public leaderboards never match my actual workload, so benchmarking on my own traces is the only number I trust. throwing a messy agent trace at this tonight.

Jaime Enrique Lincovil Curivil 的头像
Jaime Enrique Lincovil Curivil3 个月前

Nice

Whisper Create 的头像
Whisper Create3 个月前

is this free?

Nitish Pandey 的头像
Nitish Pandey3 个月前

@grok how is pairwise judging approach (as mentioned in the post) automated ? or is it manual ? how is it done ? tell me in detail

Deyu Wu 的头像
Deyu Wu3 个月前

This is very useful for companies struggling to catch up with the model race. The difficulty is not selecting the model, it is building your own eval. Great launch!

zhod 的头像
zhod3 个月前

Good stuff AA

Ella Tech & Tool 的头像
Ella Tech & Tool3 个月前

This is huge Custom benchmarks cost/time metrics is exactly what teams need

Aiden Milan 的头像
Aiden Milan3 个月前

Finding a model that’s 10x cheaper or faster for your specific task is more useful than another public leaderboard flex.

Aviv Steiner 的头像
Aviv Steiner3 个月前

Can I optimize cached input tokens where applicable and take it into account in the benchmark?

GG WP Brawl Stars 的头像
GG WP Brawl Stars2 个月前

You're on the payroll! You're hiding GLM 5.3.

Ricci Research 的头像
Ricci Research3 个月前

The real benchmark isn’t who tops a leaderboard—it’s who survives your workload without setting your token budget on fire.

Ian Lucas 的头像
Ian Lucas3 个月前

Cool idea! When it says "bring your own agent," can that include our own harness? Could we run the same model through multiple harnesses?

Artificial Analysis 的头像
Artificial Analysis2 个月前

Yes, exactly - you can run a eval on model(s) running in your own agent harness. We expose a HTTP endpoint for you to send outputs to Optima that can then be evaluated

Ian Lucas 的头像
Ian Lucas2 个月前

nice!

Mr. Walker 的头像
Mr. Walker3 个月前

The cost-per-task and latency tracking is the part that actually matters. Once people start ranking models on their own agent traces instead of public benches, a lot of the current “top model” rankings are going to look very different.

Code is a Battlefield 的头像
Code is a Battlefield3 个月前

Optima von Artificial Analysis ist unspektakulärer als „NEUES MODELL!!!“ – und wahrscheinlich wichtiger. Denn öffentliche Benchmarks fragen: Wer gewinnt unseren Test? Eigene Benchmarks fragen: Wer gewinnt meinen tatsächlichen Anwendungsfall? Das klingt nach einer kleinen methodischen Änderung. Für Modellrankings ist es eher der Moment, in dem der Teppich weggezogen wird. Plötzlich zählt nicht mehr, wer auf der Bühne die schönste Zahl hochhält, sondern wer bei der echten Arbeit liefert. Marketingabteilungen entdecken gerade vermutlich eine neue Benchmark: Fluchtgeschwindigkeit zum Notausgang.

ThirdWorldAmerican 的头像
ThirdWorldAmerican3 个月前

Cool

Maziyar PANAHI 的头像
Maziyar PANAHI3 个月前

very interesting! i have edge evals for clinical and biomedical tasks, ranging across safety/classification/longevity/medical reasoning. i have kept it private because i don't want this to be contaminated. how private can the evals be on Optima?

Kevin Morales 的头像
Kevin Morales3 个月前

The use case I'd benchmark first is boring and unglamorous: which model reads a photographed restaurant menu in Spanish and returns clean dish/price JSON. Public leaderboards never tell me that, and it's the only number that decides my model spend.

相关视频

how to use claude code mods like a top 1% user, step by step: give this to your agent before everyone catches on👇 1. set up Jev connect Jev to the model registry you want to use. check that the connection works and the listed models are available. 2. build your claude code mod open claude code 2.1.287 or later and paste this prompt: “build a mod called run-ledger. load plugin-authoring and use the API types for my installed version. create a dashboard that shows: - estimated cost per run, model, and source plugin where known - which model handles each task - each subagent’s status, latest action, and elapsed time include token counts, cache usage, and reported retries. count each request once. keep background tasks linked to their original run. use dated prices. label costs as API estimates, not subscription charges. show unknown when data is missing. connect the mod to my existing Jev setup. give Jev the task, available models, prices, budget, and relevant past results. ask it to recommend a model and explain why. start with recommendations. make automatic routing optional for eligible subagents. show the recommended model, actual model, result, and cost. include Jev’s own cost. keep state across hot reloads. add details and export. the dashboard itself must make no model calls. validate the plugin. test rendering, costs, attribution, and duplicate counting. give me steps for a live test.” 3. test the setup allow hot reload when prompted. run a simple task, a subagent task, and a mod-triggered model call. check that the dashboard updates, each request counts once, and Jev’s recommended model can actually run the task. 4. install the working mod ask claude to copy it out of the temporary folder and install it as a persistent plugin. see the cost. choose the model. check the result.

Avid

47,276 次观看 • 1 个月前