SevaVaani-Worker

Performance Optimization – Sevavaani Worker & Backend
The initial implementation of the system had several performance bottlenecks due to inefficient data handling and synchronous processing. Frequent redundant database queries, over-fetching of unnecessary data, and blocking operations led to high response times and instability. On the frontend, improper lifecycle handling caused duplicate API calls, while navigation and search logic further added to performance overhead.
Key Issues

• Redundant database queries increased latency and server load
• Over-fetching of complete datasets even when partial data was sufficient
• Synchronous operations blocking workers, causing restarts
• Duplicate API calls due to improper useEffect handling
• Inefficient navigation leading to unnecessary stack growth
• Backend-dependent search increasing response time and load

Optimizations Implemented
Significant improvements were made by restructuring both backend and frontend logic. Data fetching was optimized to reduce redundancy, asynchronous processing was introduced to improve speed, and concurrency handling was enhanced to ensure system stability under load.

Backend Improvements

• Reduced redundant queries and filtered only required data
  → getAllJobs improved from ~13s to ~0.43s
• Optimized client data fetching using selective retrieval
  → get-chatlist improved from ~9.56s to ~1.9s
• Introduced asynchronous data fetching to parallelize operations
  → reduced from ~6.24s to ~1.15s
• Enabled concurrency using gevent for non-blocking execution
  → stable handling of ~1000 concurrent connections

Frontend Improvements

• Prevented duplicate API calls using controlled useEffect logic
• Implemented global context caching to reuse fetched data
• Optimized navigation to avoid redundant screen pushes
• Implemented client-side search using filtering to eliminate repeated backend calls

Additional Enhancements

• Implemented search across jobs, requests, and chat
• Added Help & Support modal with email integration
• Linked the About Us section to the project repository

Earlier, while registering a new user, they need to verify the phone number, but this process required the OTP service to be continuously active on my local machine (which was not possible). So I removed that dependency and introduced a simple worker registration. Give it a try and let me know your feedback.
Guys, for your convenience, I have created a combined working video of my application..Enjoyyy

In this phase, I worked on sending quotation to jobs, and then viewing “My Requests”

• Once job is assigned, It will appear in “My Jobs”
• While completing job, unique QR will be generated, which will be shown to client
• Offline app interactions using async storage and syncing logic
• Aadhar based worker verification
• Corresponding backend apis in Python Flask