PHPMem v2.0.1
Version
1.6.45
Uptime
15 days 19 hours 18 minutes 23 seconds
Memory
Total
512MB
Used
9,38MB (1.83%)
Free
502,62MB
Keys
Current
11 436
Total (since start)
35 066
Evictions
0
Reclaimed
738
Expired Unfetched
0
Evicted Unfetched
0
Connections
Current
6 / 1 024 max
Total
178 896
Rejected
0
llm:c7995b579e79c1af1b57157ead7d54086c116c5120234cf77f77f8753072946a
Edit
This dataset delivers a complete, single-table snapshot of 9,551 restaurant records from the Zomato platform with zero missing values across all fields—a rare 100% completeness score that enables immediate analysis without imputation or cleanup overhead. The data supports robust profiling of restaurant attributes, pricing patterns, cuisine distributions, and customer ratings within a self-contained structure, making it ideal for market segmentation, competitive benchmarking, and location-based opportunity mapping. However, the absence of foreign key relationships means this is a static catalog: you cannot trace customer behavior over time, link orders to outlets, or analyze repeat patronage. The single most important limitation is architectural, not quality—this dataset describes *what exists* (restaurant inventory and characteristics) but not *what happens* (transactions, reviews, or operational events).
**What this data enables:** Immediate cross-sectional analysis of restaurant density by geography, cuisine popularity, price-point distribution, and rating correlations. You can answer "Which neighborhoods have the highest concentration of highly-rated budget restaurants?" or "What cuisine types command premium pricing?" with full confidence in data integrity. **What it cannot support:** Temporal trends, customer journey analysis, revenue forecasting, or any question requiring event history or relational context beyond the restaurant entity itself. Treat this as a high-fidelity market census, not a transactional system of record.