Feature #6755
openPerformance increase for google addressing 2X speed up Api
Start date:
01/10/2026
Due date:
01/16/2026 (13 days late)
% Done:
80%
Estimated time:
8:00 h
Spent time:
Description
1. Redis Caching (The 2X+ Speedup)
Instead of asking Google for the same address every time, you store the result in Redis for a few hours. Since Redis is "in-memory," it responds in milliseconds compared to Google’s ~200-500ms.
Note: Google’s Terms generally allow caching the place_id and formatted addresses for temporary performance, but you shouldn't store them permanently.
2. Debouncing (The "Wait and See" Strategy)
On the frontend, don't send a request for every single letter Thirupathi types. Wait for a small pause (e.g., 300ms). If a user types "Bangalore" quickly, you send 1 request instead of 9.
Subtasks
Related issues
Updated by Thirupathirao Uppu 19 days ago
- Status changed from New to In Progress
- Priority changed from Normal to Immediate
- % Done changed from 0 to 80