Distributor demo storefront, built on the PIMento API Sign in

Machines

No products here

Nothing is published in this category on this tenant.

API reads behind this page 5 over the wire, 2 from cache · 360 ms total
Method Path Source Status Time
GET /v2/categories/-1 network 200 13 ms
GET /v2/categories/-1/subcategories network 204 32 ms
GET /v2/categories/100 network 200 51 ms
GET /v2/categories/-1/products?$top=24&$skip=0 network 204 92 ms
GET /v2/products?$filter=requireLogin%20eq%20true&$select=productId&$top=100 network 200 171 ms
GET /categories cache 15m — —

204 and 404 both mean “no rows” on this API — which of the two an endpoint uses is per-endpoint, and the client maps both to an empty result rather than an error. Collections come wrapped in an OData envelope and are capped at 100 rows per page.

Rows marked cache were answered from memory, and the time beside each is how long that kind of read is held; one marked asked twice is something this page had already read while rendering, so it cost nothing either way. Catalog reads are cached by rate of change rather than on one site-wide timer:

Pricing and stock are read live on every view — there is no setting that caches them. That is why a warm product page still makes exactly one request: everything else on it came from memory.

The catalog can also drop all of it at once rather than waiting for a tier to lapse, by calling POST /hooks/cache when it publishes.