You could try caching your results, or even store them in the table, or related table. If the ads location doesn’t change, there doesn’t seem to be a need to call the api every single time. Additionally, if the results aren’t needed right away, you could queue the job of calling the api, such that even if the api round-trip takes a while, the user can continue uninterrupted, while the queued job does the work of fetching and storing the results.
Benny On Feb 1, 2021, at 11:07 PM, Salima Begum <[email protected]> wrote: Thank you everyone. We identified the issue. Basically we are using an API which calculates distance between two different ads using zip code value and this help us to show the distance of the ad from logged-in users location. So when classifies page is being loaded, this API is called for each and every. Ad and taking time to process distance calculation for each Ad. So we need to avoid this somehow and we are looking for any advanced method or package to achieve this. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAMSz6b%3DzPyf8_p8zxKw2DRMpcdmVeVXoAaSGnxo%2BLa4t2yaTQg%40mail.gmail.com<https://groups.google.com/d/msgid/django-users/CAMSz6b%3DzPyf8_p8zxKw2DRMpcdmVeVXoAaSGnxo%2BLa4t2yaTQg%40mail.gmail.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CH2PR14MB3913BDBA42CF0F356DDCD8D6C0B59%40CH2PR14MB3913.namprd14.prod.outlook.com.
