victorious-parrot-47014
06/05/2023, 7:37 AMvictorious-parrot-47014
06/05/2023, 7:39 AM1. request duration: 5084 ms, url=/catalog-search?page=5&include=abstract-products, status=200
2. request duration: 65 ms, url=/catalog-search?page=133&include=abstract-products, status=200
3. request duration: 71 ms, url=/catalog-search?page=2&include=abstract-products, status=200
4. request duration: 67 ms, url=/catalog-search?page=17&include=abstract-products, status=200
5. request duration: 60 ms, url=/catalog-search?page=109&include=abstract-products, status=200
6. request duration: 65 ms, url=/catalog-search?page=86&include=abstract-products, status=200
7. request duration: 57 ms, url=/catalog-search?page=58&include=abstract-products, status=200
8. request duration: 59 ms, url=/catalog-search?page=56&include=abstract-products, status=200
9. request duration: 55 ms, url=/catalog-search?page=50&include=abstract-products, status=200
10. request duration: 86 ms, url=/catalog-search?page=128&include=abstract-products, status=200
brave-article-83943
06/05/2023, 8:02 AMI noticed that HTTP requests to the glue api via Postman are much faster (especially locally) cf. 100ms vs 5000ms.It's not quite clear what are you comparing. Local vs Cloud? Or Postman vs something else? From the set of results you published (if they are from the same environment) seems like the first query is slower because the cache is not warmed up yet
victorious-parrot-47014
06/05/2023, 8:37 AMbrave-article-83943
06/05/2023, 9:13 AMSo probably that also means that cache needs to warm up every single timeThat should not be the case, it's enough to warm it up once with console commands or calling the endpoint