leanprover-community / leanprover-community/repl

Server mode

Open
#84 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lean
Stars
228
Forks
69
Avg merge
15m
Merged PRs (30d)
4

Description

Hi!

In the recent Kimina-Prover paper is mentioned:

Lean Server. In our reinforcement learning and evaluation pipelines, we integrate the Numina Lean Server (Numina
2025) as the verification backend to provide real-time feedback for generated proof attempts. Built upon Lean FRO’s
LeanREPL (Lean FRO 2023), the Numina Lean Server employs an LRU-based caching mechanism that reuses
preloaded environments based on import headers, significantly reducing initialization overhead. Furthermore, it
supports extensive parallelization across multiple CPUs by managing multiple Lean REPL processes concurrently.
These innovations result in a 10× speedup in verification throughput, achieving up to 100 iterations per second on
machines equipped with 64 CPU cores and 512 GB RAM. 

Would you have an advise what they might mean by LeanRepl preloaded environments (based on imports)?

In effect, what would be the fastest way of initializing LeanRepl process instances, given some known imports?

E.g. is it possible to do some kind of forkserver and simply clone process once it's done loading the imports? Or is there another way of snapshotting the Lean REPL state and quickly loading / resetting to it?

For Lean-in-the-loop proof generators it's very important to have a lightning-fast LeanRepl server interface which can be deployed to a big machine and manage LeanRepl workers in the most efficient way (e.g. they should fast super-fast and maybe have a pre-ready pool of LeanRepl worker processes)?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no repository files, tests, or entry points. Start by identifying the existing Lean REPL process initialization path, then turn the proposed forkserver, snapshot, or worker-pool alternatives into a scoped design with measurable initialization and reset behavior; completion criteria are not specified.

Written by the indexing model from the issue text.

Assessment

Domain
backend, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.