PHPMem v2.0.1
Version
1.6.45
Uptime
7 days 6 hours 34 minutes 27 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
2 / 1 024 max
Total
61 966
Rejected
0
llm:b3b89a517471bae5cc6113d0915f547bdc89757c871c339e0104e0ac789cc7df
Edit
This dataset delivers 2,912 rows of boxing intelligence across two unlinked tables—**fighters** (2,760 rows, 95% of volume) and **popular_matches** (152 rows)—with near-perfect 99% completeness and no structural integrity violations to repair. The architecture supports single-table fighter profiling at scale but cannot natively connect athlete attributes to match outcomes: no foreign keys bridge the two tables, meaning predictive modeling of "which fighter features separate winners from losers" will require manual linkage through fighter names or external identifiers before any pre-fight attribute can be statistically tied to a win-loss record. This is the critical gap between the dataset's current state and the stated analytical goal.
What the data *does* enable immediately is comprehensive fighter characterization—stance distributions, reach advantages, weight-class clustering, and career trajectory patterns within the 2,760-row roster—and isolated match-level outcome analysis within the 152 popular bouts. What it cannot do without engineering effort is answer causal or correlational questions that span both tables: you can profile fighters and you can study match results, but you cannot yet model how the former predicts the latter. For exploratory segmentation and fighter benchmarking, the dataset is production-ready; for outcome prediction, it requires a join strategy before any supervised learning pipeline can ingest it.