|
18 | 18 | Overview
|
19 | 19 | --------
|
20 | 20 |
|
21 |
| -|charts| is metered based on the volume of data |
22 |
| -transferred from the |charts-short| web server to web browser clients. |
23 |
| -MongoDB provides each |charts-short| instance with a free ``1 GB`` of |
24 |
| -data transfers per month. You can view your |charts-short| instance's |
25 |
| -monthly data usage in the :ref:`Data Transfer <admin-usage>` page. |
26 |
| -To visualize your |charts-short| usage, you can create a |
27 |
| -:ref:`Billing Dashboard <billing-dashboards>`. |
28 |
| - |
29 |
| -The free usage tier provides approximately 500,000 chart |
30 |
| -renders over a month. However, this number may vary based on the types |
31 |
| -of charts being rendered. A number chart or a bar chart with few bars |
32 |
| -typically consumes less data, while a scatter chart with many |
33 |
| -data points or a large table could consume more. |
34 |
| - |
35 |
| -Once the ``1 GB`` of free data usage has been consumed, MongoDB bills |
36 |
| -Charts data transfers at a fixed rate of **$1.00 per GB**. |
37 |
| - |
38 |
| -In addition, any applicable |service| data transfer fees apply, as per |
39 |
| -the :guilabel:`Data Transfer Fees` section of the |
40 |
| -`Atlas Pricing <https://www.mongodb.com/pricing>`__ page. |
41 |
| -|charts-short| is hosted on |aws| ``us-east-1`` region, and |
42 |
| -uses this region to calculate the fees. |
43 |
| - |
44 |
| -Sample Pricing Scenarios |
45 |
| ------------------------- |
46 |
| - |
47 |
| -The following examples show the expected monthly charge for different |
48 |
| -usage scenarios. Consider: |
49 |
| - |
50 |
| -1. A |charts-short| instance with 5 users, each of whom refreshes a |
51 |
| - 10-chart :ref:`dashboard <dashboards>` once an hour during business |
52 |
| - hours. This results in about 8,000 renders over |
53 |
| - the month, and easily falls within the ``1 GB`` free tier. |
54 |
| - |
55 |
| - | |
56 |
| - |
57 |
| -2. A dashboard on a large-screen display with 20 charts set to refresh |
58 |
| - every 5 minutes, all 24 hours of the day. This results in about |
59 |
| - 300,000 renders over the month. Assuming these charts are not |
60 |
| - abnormally large, this scenario also falls entirely within the |
61 |
| - ``1 GB`` free tier. |
62 |
| - |
63 |
| - | |
64 |
| - |
65 |
| -3. A *large* chart embedded on a web page that receives 10,000 views |
66 |
| - per day, resulting in 300,000 renders over the month. This chart |
67 |
| - takes roughly five times as much data to render compared to a |
68 |
| - typical chart, and consumes ``3 GB`` of data over the month. |
69 |
| - |
70 |
| - The first ``1 GB`` is free, and the remaining ``2 GB`` is billed at |
71 |
| - $1.00 per GB, resulting in a total cost of $2.00 for the month. |
72 |
| - |
73 | 21 | The following table specifies the features available in |charts-short|
|
74 | 22 | based on the type of clusters you have in your |service| project:
|
75 | 23 |
|
|
0 commit comments