PHPMem v2.0.1

Version
1.6.45
Uptime
15 days 12 hours 53 minutes 23 seconds

Memory

Total
512MB
Used
9,60MB (1.88%)
Free
502,40MB

Keys

Current
11 839
Total (since start)
35 066
Evictions
0
Reclaimed
734
Expired Unfetched
0
Evicted Unfetched
0

Connections

Current
16 / 1 024 max
Total
174 020
Rejected
0
llm:85b618e51e513a90e5559259c584b8cae9099d8177c8dbfd9dfd3901b8686b98
TTL 6 days 17 hours 28 minutes 6 seconds Size 1,44KB Export
Edit
**Size:** The dataset has 5 tables and 718,470 rows in total. | Table | Rows | |---|---| | raw_kaggle | 237,205 | | return_kaggle | 237,196 | | serve_kaggle | 237,185 | | players_tournament_man_ | 6,422 | | players_man_ | 462 | **Columns:** The two sources I checked disagree: - The catalog overview (`analytics.table_overview`) reports 17 columns for each of the three match tables, 4 for players_tournament_man_ and 3 for players_man_. That is 58 in total. - The dataset card lists 21, 21, 21, 8 and 7 columns for the same tables, which is 78 in total. The difference may come from how the metadata profiler counts columns. I did not resolve it by listing the columns table by table, so treat 58 to 78 as the range. **Time period:** The data does cover time. - The three match-level tables (raw_kaggle, return_kaggle, serve_kaggle) store `Date` as text. I parsed it, and every row converted successfully: 237,205, 237,196 and 237,185 rows respectively. Each table spans **13 Aug 2001 to 28 Oct 2024**. - The earlier ranges on the card (for example 2013 to 2024) came from sorting the text values, so they are unreliable. - `players_tournament_man_.year` runs from **2002 to 2024**. - `players_man_.playing_years` is also text, and I did not parse it. Overall, the data covers about 23 years of men's professional tennis, from 2001 to late 2024.