Timmy_Foundation/hermes-agent
15
0
Fork 0
Code Issues 65 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

[Memory P5] Memory performance budget enforcement #256

New Issue
Closed
opened 2026-04-09 00:42:33 +00:00 by Rockachopa · 0 comments
Rockachopa commented 2026-04-09 00:42:33 +00:00
Owner
Copy Link

Context

Memory retrieval runs before every turn. If it's slow, every interaction feels slow. Need strict performance budgets.

Task

  1. Define budgets:
    • Total prefetch latency: <200ms
    • Tier 1 (semantic): <50ms
    • Tier 2 (operational): <10ms (file read)
    • Tier 3 (episodic probe): <10ms (FTS5 count)
    • Total injected tokens: <2000
  2. Measure actual latency with all tiers active
  3. Optimize: parallel prefetch across tiers
  4. Token budget allocation: semantic 1000, operational 500, episodic 500
  5. Enforce budgets with timeouts and token truncation

Acceptance Criteria

  • All tiers complete prefetch in <200ms combined
  • Injected context never exceeds 2000 tokens
  • Performance metrics logged per turn
  • Graceful degradation if a tier is slow (skip it, don't block)

Part of: [EPIC] Unified Memory Architecture

## Context Memory retrieval runs before every turn. If it's slow, every interaction feels slow. Need strict performance budgets. ## Task 1. Define budgets: - Total prefetch latency: <200ms - Tier 1 (semantic): <50ms - Tier 2 (operational): <10ms (file read) - Tier 3 (episodic probe): <10ms (FTS5 count) - Total injected tokens: <2000 2. Measure actual latency with all tiers active 3. Optimize: parallel prefetch across tiers 4. Token budget allocation: semantic 1000, operational 500, episodic 500 5. Enforce budgets with timeouts and token truncation ## Acceptance Criteria - All tiers complete prefetch in <200ms combined - Injected context never exceeds 2000 tokens - Performance metrics logged per turn - Graceful degradation if a tier is slow (skip it, don't block) Part of: [EPIC] Unified Memory Architecture
Rockachopa added this to the Unified Memory Architecture milestone 2026-04-09 00:42:33 +00:00
Rockachopa added the phase:5-integrationepic:memory labels 2026-04-09 00:42:34 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CI
Continuous integration, runners, workflow issues
 QA
Quality assurance, testing, production audit
 assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Task assigned to KimiClaw for processing
 blocked
Blocked by external dependency or merge conflict
 claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 duplicate
Duplicate of another issue
 epic
Epic - large feature with multiple sub-tasks
 epic:memory
Unified Memory Architecture epic
 gaming
Gaming agent capabilities
 infra
Infrastructure, VPS, DNS, deployment
 kimi-done
KimiClaw has completed this task
 kimi-in-progress
KimiClaw is actively working on this
 mcp
MCP (Model Context Protocol) tools & servers
 morrowind
Morrowind Agent gameplay & MCP integration
 needs-review
PR or issue requires reviewer sign-off before merge/close
 p0-critical
p1-important
phase:1-activate
Phase 1: Activate existing systems
 phase:2-operational
Phase 2: Operational memory bridge
 phase:3-episodic
Phase 3: Proactive episodic recall
 phase:4-hygiene
Phase 4: Memory hygiene and quality
 phase:5-integration
Phase 5: Integration and testing
 security
Security hardening, vulnerability fixes
 stale
No activity, pending triage or closure
 velocity-engine
Auto-generated by velocity engine
 wont-fix
Closed as intentionally not fixing — explicit descope
No Label epic:memory phase:5-integration
Milestone
No items
No Milestone Unified Memory Architecture
Projects
Clear projects
No project
Assignees
Clear assignees
Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok hermes kimi manus perplexity sonnet
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/hermes-agent#256
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?