PHPMem v2.0.1
Version
1.6.45
Uptime
7 days 12 hours 40 minutes 21 seconds
Memory
Total
512MB
Used
13,33MB (2.6%)
Free
498,67MB
Keys
Current
10 164
Total (since start)
11 094
Evictions
0
Reclaimed
157
Expired Unfetched
0
Evicted Unfetched
0
Connections
Current
4 / 1 024 max
Total
68 080
Rejected
0
llm:58a0f21b51fb7a2af8d28dab1b4f7540a9904ceb910de3fec7477fb7af2bfe8c
Edit
```xml
<result>
<column_name>duration_ms</column_name>
<family>additive</family>
<subtype>ordinal_additive</subtype>
<confidence>0.85</confidence>
<requires_user_confirmation>false</requires_user_confirmation>
<sum_meaningful>true</sum_meaningful>
<signed>false</signed>
<reducers>
<primary_reducer>sum</primary_reducer>
<valid_reducers>sum, mean, min, max, median, count, distribution</valid_reducers>
<excluded_reducers>product (not a ratio), geomean (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>true</multiplicative_partner_derivable>
<reasoning>
Gate prior: PATH table with sequence axis allows both multiplicative and ordinal_additive. Column name "duration_ms" with unit "ms" (milliseconds) is a physical extensive quantity (time duration), strongly signaling additive family. The measure represents instantaneous duration at each sequence step on a PATH table - summing across entities at a fixed timestamp is meaningful, but summing along the sequence axis would be inappropriate (you don't add durations across time steps). Center far from 1.0 (mean=24434, median=545), large unbounded range (max=6.5M), and presence of zeros all confirm additive. High log_symmetry_gain (19.45) suggests log-normal distribution typical of durations, not multiplicative ratios. Classification: ordinal_additive because this is a physical level quantity on a PATH table where cross-entity aggregation uses sum but sequence-axis aggregation requires normalization.
</reasoning>
<table_type_conflict>false</table_type_conflict>
</result>
```