expert-lsp/expert

Debounce project compilation

Open

#672 opened on May 8, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Elixir (1,986 stars) (103 forks)batch import
enhancementgood first issue

Description

Some users report that Expert recompiles and reindexes the project too often. In particular, it seems coding agents can launch an LSP(including expert), and when making tons of edits they save a lot of files in quick succession, apparently causing a lot of CPU load.

I think debouncing the project compilation + indexing every few seconds can help with that use case.

Contributor guide

Tech stack
elixir
Domain
performancebackend
Issue type
performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
ElixirDebouncing concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Investigate how project compilation is triggered in the LSP server. Look for modules related to compilation and indexing, likely in the lib/expert/ directory. Consider adding a debounce mechanism using a timer or GenServer to batch save events before triggering recompilation. Review any existing configuration for debounce intervals and test with rapid file saves.