Closed manumoreira closed 8 months ago
Here's the loop that traverses the whole address book for the project, which can grow to be large when using Surveda (we got +2M contacts some times).
This is, however, not used during normal Survda operation - that code is only used when queueing calls from the Project view page in Verboice itself (/projects/:id
), and not via the API.
I've just confirmed in Surveda Africa (running Verboice 3.5.1) that queueing a call from Projects (with 86k contact addresses) takes ~5.2 seconds (spending 5 seconds in this first loop - of which "only" 450ms where in ActiveRecord), but queuing a call in that same project via Surveda only took 260ms.
So there's an optimization to be done in the Project Controller, but it's not a major issue for Surveda itself.
closed by #945
For Verboice clients that drive Verboice programmatically, the address book is an unused feature that penalizes their performance