PHPMem v2.0.1

Version
1.6.45
Uptime
15 days 12 hours 51 minutes 41 seconds

Memory

Total
512MB
Used
9,60MB (1.88%)
Free
502,40MB

Keys

Current
11 841
Total (since start)
35 066
Evictions
0
Reclaimed
732
Expired Unfetched
0
Evicted Unfetched
0

Connections

Current
14 / 1 024 max
Total
173 949
Rejected
0
llm:15065b5959c571bca71b2e6de81fc43380541324a5ecb3fa366a046deb3bb0d3
TTL 6 days 4 hours 2 minutes 7 seconds Size 1,07KB Export
Edit
### 5.1 Performance Posture The Iris table (150 rows) is comfortably within the range where storage layout and query speed are not a concern. With completeness at 100% and only one table in scope, there is no cross-table movement to slow analysis, and the largest-table share of 100% simply reflects that everything lives in a single place. No scaling pressure is visible in the evidence, and we see no basis for tuning at this size. ### 5.2 Key Optimizations | Priority | Table | Recommendation | |---|---|---| | None | Iris | No optimization recommended at current data scale | No high-priority items were identified, so there is no performance spend to justify today. Any tuning at 150 rows would add complexity without a measurable benefit to analysis turnaround. The more useful planning question is how the Iris table might grow, for example through additional records or enrichment columns. Performance should be revisited if that volume increases materially.