Skip to content

Say where Token Factory sped up the work and which Nebius services are used #110

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
shipmill-romamo merged 1 commit into from
Oct 26, 2026
Merged

Say where Token Factory sped up the work and which Nebius services are used #110

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,6 +113,14 @@ How Nemotron and Token Factory are used:
model's calls from a real run's recorded output, so any model can be
tried on a real incident again and again without a host. The hosted demo
runs that way
- **Token Factory sped up the work.** Its OpenAI-compatible tool calling
worked on the first call for all four Nemotron models, so trying another
model is one string, and the 40-run evaluation needed no GPUs or model
deployment of our own
- **Other Nebius services.** Token Factory is the only one at runtime. The
evaluation is also packaged as a container for a Nebius Serverless Job
([Dockerfile](evaluations/nemotron-incident/Dockerfile)); we could not run
it there, because AI Cloud was not activated for our tenant

Try it without a server, from a clone of this repository, with a
[Token Factory](https://tokenfactory.nebius.com) API key:
Expand Down
Loading