PHPMem v2.0.1
Version
1.6.45
Uptime
7 days 20 hours 37 minutes 23 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
73 452
Rejected
0
llm:b080acfcda8574a53eead423aa38ce04810a4767e3dd4ff912d3f0c535a43fca
Edit
```json
{
"table_name": "ip_geo",
"primary_key": "ip",
"candidates": [
{
"rank": 0,
"partition_key": "ip",
"partition_key_label": "primary_identifier",
"partition_key_reasoning": "ip is the unique identifier for this dimension table with RPUV=1.00 (207 unique values for 207 rows), 100% uniqueness, and 0% nulls. Each IP address has exactly one geolocation record. This is the natural primary key for a dimension table storing IP-to-location mappings.",
"clustering_key": null,
"clustering_key_label": null,
"clustering_key_reasoning": "Dimension tables typically do not require clustering keys. The table is small (207 rows) and serves as a lookup reference for IP geolocation data. No internal ordering is needed.",
"world_line": null,
"session_column": null,
"confidence": "HIGH",
"notes": "This is a classic dimension table storing IP geolocation reference data. The ip column is the natural primary key. The resolved_at timestamp indicates when each IP was resolved, but this is metadata about the lookup process, not a temporal axis for analysis. The high null percentage (57.49%) in geographic fields suggests many IPs (likely private/internal addresses like 10.42.0.x) could not be geolocated. The table serves as a lookup reference for other tables that may contain IP addresses."
}
]
}
```