Skip to content

feat(lore): raise memory limit to 2G for transformer NER#17

Merged
amitpaz1 merged 1 commit into
mainfrom
feat/lore-transformer-ner-memory
Jul 3, 2026
Merged

feat(lore): raise memory limit to 2G for transformer NER#17
amitpaz1 merged 1 commit into
mainfrom
feat/lore-transformer-ner-memory

Conversation

@amitpaz1

@amitpaz1 amitpaz1 commented Jul 3, 2026

Copy link
Copy Markdown
Member

Lore now defaults to en_core_web_trf (transformer NER — see agentkitai/lore#100) which loads torch + RoBERTa and needs ~1.5 GB RAM. The previous 256 M limit OOM-killed the container on model load (OOMKilled=true, entity extraction silently died).

  • Raise the lore service memory limit 256M → 2G.
  • Add LORE_GRAPH_SPACY_MODEL (default en_core_web_trf) as an overridable env so it can be dialed down to en_core_web_sm/lg for a smaller footprint (lower the limit to ~512M then).

Verified locally: with 2G, OOMKilled=false, and extraction persists transformer-typed entities (Sarah→person, MongoDB→technology, AWS→organization).

🤖 Generated with Claude Code
https://claude.ai/code/session_01CKkfVA3iY5G3Q43Mg4Xsu2

…_trf)

Lore now defaults to the en_core_web_trf spaCy model (transformer NER), which
loads torch + RoBERTa and needs ~1.5GB RAM. The old 256M limit OOM-killed the
container on model load. Raise to 2G, and surface LORE_GRAPH_SPACY_MODEL as an
overridable env (default en_core_web_trf) so it can be dialed down to
en_core_web_sm/lg (and the limit lowered) for a smaller footprint.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CKkfVA3iY5G3Q43Mg4Xsu2
@amitpaz1
amitpaz1 merged commit 24e220c into main Jul 3, 2026
1 check passed
@amitpaz1
amitpaz1 deleted the feat/lore-transformer-ner-memory branch July 3, 2026 11:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant