Usage
Billable consumption, cost drivers, and regional demand for the selected environment.
| Resource | Total | Included | Billable | Estimated cost |
|---|---|---|---|---|
| Invocations | 1,284,004,118 calls | 500,000,000 calls | 784,004,118 calls | $156.80 |
| Compute time | 8,412,006 seconds | 2,000,000 seconds | 6,412,006 seconds | $115.42 |
| Durable state | 14,882 GiB months | 500 GiB months | 14,382 GiB months | $1,725.84 |
| Data transfer | 41,204 GiB | 1,000 GiB | 40,204 GiB | $3,618.36 |
4 metered resources in the selected environment
Usage over time
Consumption across this period, against the period before it.
Cost drivers
The part of the estimate worth acting on, ordered by cost.
| Resource | Estimated cost | Share of the estimate | Change |
|---|---|---|---|
| Battle room readsInvocations | $2,134.00 | 38% | Up 12% |
| Wallet storage held past 30 daysDurable state | $1,348.00 | 24% | Up 31% |
| Room media egressData transfer | $1,067.00 | 19% | Down 4% |
Geographic usage
Where the calls arrived. Choosing a region turns the globe to it.
44% of requests, 2390 homes held, 18,204 GiB out
31% of requests, 903 homes held, 12,880 GiB out
25% of requests, 311 homes held, 10,120 GiB out
Optimization history
Changes the runtime applied on its own, and the ones it is recommending.
- Battle room reads answered from a shorter-lived cache96,400,000 calls avoidedRecommended 22 hours ago
Fourteen days of reads show the same room requested a median of 9 times inside 30 seconds. Holding a room for that long would answer 8 of the 9 without a call.
- Replica reads moved closer to European callers12,400 GiB avoidedApplied by the runtime 3 days ago
Amsterdam served 31% of calls against a readable replica in Ashburn. Adding a replica in the region the callers are in stopped the round trip.