In the following table you may find processing duration measurements taken based on a variety of test cases for each endpoint. This information can assist you when planning the utilization of Placer API.
Retry triggering
The system is built in a manner that it uses a caching mechanism for reports. As reports producing duration may take a while the system will first verify the reports caching. If the report is found then it will be immediately returned in the response. Otherwise, you will be getting the indication of IN_PROGRESS response (http-code=202) and would be asked to re-trigger the same report for receiving the full report. It is recommended to be advised of the duration estimates above when planning the retry mechanism when utilizing reports’ endpoints.
⏱Processing duration statistics
| Report Name | # entities | Date range (Years) | Granularity | Scope | Region | Average processing time(sec.) |
|---|---|---|---|---|---|---|
| Ranking Index - Closely Ranked | 1 | N/A | N/A | category | nationwide | 5.37 |
| Ranking Index - Closely Ranked | 1 | N/A | N/A | chain | nationwide | 5.26 |
| Ranking Index - Closely Ranked | 1 | N/A | N/A | groupCategory | nationwide | 5.23 |
| Ranking Index - Closely Ranked | 1 | N/A | N/A | groupCategory | 15 | 3.27 |
| Ranking Index - Closely Ranked | 1 | N/A | N/A | category | 15 | 2.6 |
| Ranking Index - Closely Ranked | 1 | N/A | N/A | chain | 15 | 2.16 |
| Visitor Journey - Favorite Chains | 1 | 5 | N/A | N/A | N/A | 1.81 |
| Visitor Journey - Favorite Chains | 1 | 1 | N/A | N/A | N/A | 1.55 |
| Visitor Journey - Favorite Places | 1 | 5 | N/A | N/A | N/A | 5.04 |
| Visitor Journey - Favorite Places | 1 | 1 | N/A | N/A | N/A | 3.88 |
| Ranking metrics For Multiple properties | 100 | lastWeek | N/A | N/A | N/A | 0.62 |
| Ranking metrics For Multiple properties | 100 | year2018 | N/A | N/A | N/A | 0.6 |
| Ranking metrics For Multiple properties | 1 | lastWeek | N/A | N/A | N/A | 0.51 |
| Ranking metrics For Multiple properties | 1 | year2018 | N/A | N/A | N/A | 0.45 |
| Ranking metrics for a single property | 1 | 1 | N/A | category | 15 | 8.81 |
| Ranking metrics for a single property | 1 | 1 | N/A | N/A | N/A | 8.46 |
| Ranking metrics for a single property | 1 | 5 | N/A | category | 15 | 8.44 |
| Ranking Index - Top Ranked | 1 | N/A | N/A | groupCategory | 15 | 3.79 |
| Ranking Index - Top Ranked | 1 | N/A | N/A | category | nationwide | 2.68 |
| Ranking Index - Top Ranked | 1 | N/A | N/A | groupCategory | nationwide | 2.67 |
| Ranking Index - Top Ranked | 1 | N/A | N/A | category | 15 | 2.62 |
| Ranking Index - Top Ranked | 1 | N/A | N/A | chain | nationwide | 2.34 |
| Ranking Index - Top Ranked | 1 | N/A | N/A | chain | 15 | 2.19 |
| Trade Area Demographics Profile Report | 1 | 5 | N/A | N/A | N/A | 1.66 |
| Trade Area Demographics Profile Report | 1 | 1 | N/A | N/A | N/A | 1.5 |
| Trade Area Report | 1 | 1 | N/A | N/A | N/A | 3.15 |
| Trade Area Report | 1 | 5 | N/A | N/A | N/A | 1.32 |
| Visit Metrics Summary Report | 1 | 5 | N/A | N/A | N/A | 15.88 |
| Visit Metrics Summary Report | 1 | 1 | N/A | N/A | N/A | 10.3 |
| Visit Metrics Summary Report | 100 | 5 | N/A | N/A | N/A | 8.38 |
| Visit Metrics Summary Report | 100 | 1 | N/A | N/A | N/A | 5.46 |
| Visits by days report | 1 | 5 | N/A | N/A | N/A | 0.74 |
| Visits by days report | 1 | 1 | N/A | N/A | N/A | 0.7 |
| Visits by Dwell Time report | 1 | 5 | N/A | N/A | N/A | 0.86 |
| Visits by Dwell Time report | 1 | 1 | N/A | N/A | N/A | 0.68 |
| Visits by Hours report | 1 | 1 | N/A | N/A | N/A | 0.82 |
| Visits by Hours report | 1 | 5 | N/A | N/A | N/A | 0.75 |
| Visit Trends Report | 100 | 1 | day | N/A | N/A | 13.12 |
| Visit Trends Report | 100 | 5 | week | N/A | N/A | 10.2 |
| Visit Trends Report | 100 | 3 | week | N/A | N/A | 6.66 |
| Visit Trends Report | 1 | 5 | day | N/A | N/A | 4.14 |
| Visit Trends Report | 100 | 5 | month | N/A | N/A | 3.68 |
| Visit Trends Report | 100 | 1 | week | N/A | N/A | 3.06 |
| Visit Trends Report | 1 | 3 | day | N/A | N/A | 3.02 |
| Visit Trends Report | 100 | 3 | month | N/A | N/A | 2.75 |
| Visit Trends Report | 100 | 1 | month | N/A | N/A | 1.89 |
| Visit Trends Report | 1 | 1 | day | N/A | N/A | 1.71 |
| Visit Trends Report | 1 | 5 | week | N/A | N/A | 1.39 |
| Visit Trends Report | 1 | 3 | week | N/A | N/A | 1.25 |
| Visit Trends Report | 1 | 5 | month | N/A | N/A | 1.22 |
| Visit Trends Report | 1 | 1 | week | N/A | N/A | 1.15 |
| Visit Trends Report | 1 | 1 | month | N/A | N/A | 1.07 |
| Visit Trends Report | 1 | 3 | month | N/A | N/A | 1.02 |
Timeout troubleshooting
We have identified cases where the gateway responds with a timeout (http-code=504). Those cases are mostly requests spanning a large date range and/or narrowed granularity (i.e., day) and/or many POIs. The Placer team is working to fix this issue. Until this issue is resolved, please use narrowed time frames and/or longer granularity and/or fewer POIs within the bulk query.