PHPMem v2.0.1
Version
1.6.45
Uptime
7 days 18 hours 59 minutes 47 seconds
Memory
Total
512MB
Used
8,15MB (1.59%)
Free
503,85MB
Keys
Current
6 252
Total (since start)
11 098
Evictions
0
Reclaimed
299
Expired Unfetched
0
Evicted Unfetched
0
Connections
Current
3 / 1 024 max
Total
72 445
Rejected
0
llm:e5e5e3e0de73472905e9176bce95a97f3a8f182a44ee220a4b4cd1127e7962d6
Edit
```xml
<result>
<column_name>ingest_elapsed_ms</column_name>
<family>additive</family>
<subtype>intensive_additive</subtype>
<confidence>0.85</confidence>
<requires_user_confirmation>false</requires_user_confirmation>
<sum_meaningful>false</sum_meaningful>
<signed>false</signed>
<reducers>
<primary_reducer>mean</primary_reducer>
<valid_reducers>mean, min, max, median, p50, p95, p99, distribution</valid_reducers>
<excluded_reducers>sum (summing elapsed times across entities is meaningless), product (not a ratio)</excluded_reducers>
<average_semantics>arithmetic_mean</average_semantics>
</reducers>
<inner_outer_measure>
<inner_measure_reducer>min</inner_measure_reducer>
<outer_measure_reducer>max</outer_measure_reducer>
</inner_outer_measure>
<multiplicative_partner_derivable>false</multiplicative_partner_derivable>
<reasoning>
Gate prior: DIMENSION table with no sequence axis makes multiplicative highly implausible. Column name "ingest_elapsed_ms" indicates a duration measurement (milliseconds), which is an intensive property - each entity has its own elapsed time. The values are strictly positive with large magnitude (28 to 28719 ms) and high variance, centered far from both 0 and 1 (mean=834, median=152). This is a performance metric where averaging across entities is meaningful (e.g., "average ingest time"), but summing is not ("total elapsed time" across independent entities has no physical meaning). Classified as intensive_additive with mean as the primary reducer.
</reasoning>
<table_type_conflict>false</table_type_conflict>
</result>
```