You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What's the problem this feature will solve?
Following the community's ongoing discussions regarding exponential API latency and event-loop blocking (specifically raised by @crocmons in #200), there is a need for a reliable, reproducible benchmark to measure how memory modules behave under high-frequency, multi-agent interactions.
While #200 excellently identifies the execution-layer overhead, my testing shows that the underlying STLTMemory consolidation logic inherently exacerbates this bottleneck by forcing blocking LLM calls whenever the deque fills up.
Describe the solution you'd like
I propose adding a new Agent-Based Model example to the examples/ directory: Information Cascade (Financial Rumor Mill).
In this model, LLM-powered quantitative traders rely purely on market rumors and STLTMemory to make decisions. By deliberately constraining short_term_capacity=1, this model forces rapid, continuous memory consolidation, effectively stress-testing the memory architecture and bypassing default UI overhead.
Are you planning to open a PR for this?
Yes. I already have the model, a custom robust Solara UI (app.py), and headless benchmark scripts (run_benchmark.py) fully prepared and formatted with pre-commit locally. I will open a PR immediately following this issue.
Additional context
This example provides two massive values to the community:
Behavioral Testing: It perfectly demonstrates "Echo Chamber" hallucinations and cognitive degradation when LLMs repeatedly summarize their own outputs over long simulation runs.
What's the problem this feature will solve?
Following the community's ongoing discussions regarding exponential API latency and event-loop blocking (specifically raised by @crocmons in #200), there is a need for a reliable, reproducible benchmark to measure how memory modules behave under high-frequency, multi-agent interactions.
While #200 excellently identifies the execution-layer overhead, my testing shows that the underlying
STLTMemoryconsolidation logic inherently exacerbates this bottleneck by forcing blocking LLM calls whenever the deque fills up.Describe the solution you'd like
I propose adding a new Agent-Based Model example to the
examples/directory: Information Cascade (Financial Rumor Mill).In this model, LLM-powered quantitative traders rely purely on market rumors and
STLTMemoryto make decisions. By deliberately constrainingshort_term_capacity=1, this model forces rapid, continuous memory consolidation, effectively stress-testing the memory architecture and bypassing default UI overhead.Are you planning to open a PR for this?
Yes. I already have the model, a custom robust Solara UI (
app.py), and headless benchmark scripts (run_benchmark.py) fully prepared and formatted withpre-commitlocally. I will open a PR immediately following this issue.Additional context
This example provides two massive values to the community:
step(), providing a strict baseline to measure the success of future concurrency or memory optimization PRs.