PHPMem v2.0.1

Version
1.6.45
Uptime
16 days 5 hours 22 minutes 17 seconds

Memory

Total
512MB
Used
11,10MB (2.17%)
Free
500,90MB

Keys

Current
12 504
Total (since start)
39 318
Evictions
0
Reclaimed
758
Expired Unfetched
0
Evicted Unfetched
0

Connections

Current
13 / 1 024 max
Total
185 681
Rejected
0
llm:af12622f323bd375453b6d3f8924c2b92522c9117d14301c88a91bec0975f6b5
TTL 4 days 20 hours 36 minutes 57 seconds Size 2,44KB Export
Edit
### 1.2 Key Data Assets | Table | Role | Rows | % of Total | Size | |-------|------|-----:|----------:|-----:| | callyeah_analytics_2026_07_23 | unknown | 216 | 100.0% | 0.2 MB | The **callyeah_analytics_2026_07_23** table represents the entirety of this data asset, capturing 216 records in a single flat structure. Without additional context from column profiling, the table name suggests a time-stamped analytics extract, likely representing a snapshot of operational or engagement metrics from July 2026. This single-table architecture means all available intelligence resides in one place, eliminating the complexity of cross-table navigation but also limiting dimensional analysis without enrichment. ### 1.1 Business Data Landscape This dataset appears to be a standalone analytics extract from the Callyeah platform, delivered as a single table containing 216 observations. The naming convention—incorporating a specific date (July 23, 2026)—suggests this is either a periodic snapshot, an event log, or a campaign performance summary rather than a continuously updated operational database. With no companion tables for dimensional context (such as customer segments, product catalogs, or geographic hierarchies), the data structure indicates an export designed for point-in-time reporting rather than ongoing transactional analysis. The compact 0.2 MB footprint and modest row count point to either a filtered subset of a larger system or a summary-level aggregation rather than raw event data. ### 1.3 Data Integration Posture This dataset operates in complete isolation, with zero validated joins and no companion tables to provide dimensional context or historical depth. The 100% referential integrity score is mathematically guaranteed in a single-table environment but offers no insight into data quality across related entities. For cross-functional analytics—such as linking call outcomes to customer lifetime value, regional performance, or product mix—business leaders will need to either enrich this table with additional attributes or establish connections to external data sources. The current posture limits analysis to patterns observable within the 216 records themselves, making trend analysis, cohort comparison, and root-cause investigation dependent on whatever dimensions are already embedded as columns in the existing structure.