PHPMem v2.0.1

Version
1.6.45
Uptime
7 days 11 hours 19 minutes 46 seconds

Memory

Total
512MB
Used
13,32MB (2.6%)
Free
498,68MB

Keys

Current
10 162
Total (since start)
11 092
Evictions
0
Reclaimed
157
Expired Unfetched
0
Evicted Unfetched
0

Connections

Current
3 / 1 024 max
Total
66 782
Rejected
0
llm:5d4a9c4bd2a24155118d3da599ba74735611e27a796b7578f7d87377fac31a86
TTL 2 hours 55 minutes 44 seconds Size 1,82KB Export
Edit
```xml <result> <column_name>reach_A</column_name> <family>additive</family> <subtype>intensive_additive</subtype> <confidence>0.72</confidence> <requires_user_confirmation>true</requires_user_confirmation> <sum_meaningful>false</sum_meaningful> <signed>false</signed> <reducers> <primary_reducer>mean</primary_reducer> <valid_reducers>mean, min, max, median, distribution</valid_reducers> <excluded_reducers>sum (intensive level - summing reach values 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> DIMENSION table with no sequence axis: multiplicative highly implausible (gate prior). The column name "reach_A" suggests a spatial or network reach metric - an intensive property of each entity. Values range [5, 456] with no zeros or negatives, centered far from both 0 and 1, consistent with an absolute level measurement. High null fraction (71%) and low distinct fraction suggest this is a categorical or bucketed attribute rather than a true extensive quantity. Classified as intensive_additive because summing reach values across entities is not meaningful (you cannot add "112 reach + 147 reach"), but averaging to find typical reach is sensible. Confidence reduced due to lack of statistical moments and ambiguity in what "reach_A" measures; user confirmation recommended. </reasoning> <table_type_conflict>false</table_type_conflict> </result> ```