# FAQ: performance

### A build is slow.

A build with 200 or more files to read uses one worker process per processor core, up to 8. Set `NIRO_LOCAL_PARSE_WORKERS` to change that. Later builds handle only what changed. For scale: a full build of about 9,000 files was measured at about 103 seconds.

### Answers slow down while a build runs.

Known: questions asked without pause during a build slow the build down several times.

### A deep reverse call chain is slow.

A reverse chain 8 levels deep on a much-called name can take several seconds. Ask fewer levels (`depth=3`), or use `purpose=ASSESS_RISK` for counts.

### The graph file keeps growing.

The graph keeps a side file of recent writes (the write-ahead log), trimmed to 64 MB by default (`NIRO_LOCAL_WAL_LIMIT_MB`). A tool that holds the graph open for a long time can stop the trim. Run `niro db status` to see the size. Run `niro clean` to remove the graphs of deleted folders.

### How much disk does the graph use?

It depends on your code. `niro db status` shows it for your computer.

### How much memory and processor time does the background watcher use?

Not measured yet. It waits for file changes, and builds only after a folder goes quiet.

### `code_grep` stops early, or an answer is cut short.

A search stops after 1.5 seconds, and gives a `continue_from` value to carry on. An answer is cut at 20,000 characters. Narrow the search with `path_pattern`, or raise `NIRO_LOCAL_MAX_ANSWER_CHARS`.

### A tool call took more than 30 seconds and stopped.

One call to the engine may take 30 seconds. Ask a narrower question, or a lower `depth`.