You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en-us/cloud-services/data-stores/best-practices.md
+48Lines changed: 48 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,8 @@ description: Guidelines that help you manage your data and data stores (DataStor
5
5
6
6
Best practices are guidelines that help you manage your data more efficiently.
7
7
8
+
## General best practices
9
+
8
10
### Create fewer data stores
9
11
10
12
Data stores have similar behavior to tables in databases. When you minimize the number of data stores in an experience and put related data in the same data store, you're able to configure each data store individually and improve the service's efficiency to operate the data.
@@ -18,3 +20,49 @@ The versioning system versions individual objects instead of the entire data sto
18
20
### Use key prefixes to organize your data
19
21
20
22
Filter keys with a specific [prefix](./versioning-listing-and-caching.md#listing-and-prefixes) when calling `Class.DataStore:ListKeysAsync()|ListKeysAsync()`. For example, you can save keys with a prefix like `/User_1234/profiles/warrior` and `/User_1234/profiles/mage` in experiences that support users with multiple character profiles. You can then use a prefix search with `/User_1234/profiles` to get a list of all profiles belonging to that user.
23
+
24
+
## Optimization best practices
25
+
26
+
Data stores have storage limits that apply per experience. When your experience approaches or exceeds its quota, you should take action to reduce usage and avoid potential additional costs.
27
+
28
+
### Monitor storage usage
29
+
30
+
Use these tools for data store observability:
31
+
32
+
-**Data Stores Dashboard**, which provides you with a visual overview of your storage usage over time. Use this dashboard to monitor how your storage scales and to identify periods of unexpected growth in usage.
33
+
-**Data Stores Manager**, which gives you a direct view into your experience's stored data. The Manager includes key metrics like your current storage usage and the total keys you have stored across all of your data stores. If your experience exceeds its quota, the Manager displays an alert and your new estimated monthly cost.
34
+
35
+
If your experience has more than 100 data stores, the Manager might not display their detailed metrics. In this case, consider using programmatic analysis through Open Cloud or batch operations.
36
+
-**Notifications**, which notify you when your experience approaches or exceeds storage limits. Notifications include guidance and links to dashboards where you can then review and reduce your usage.
37
+
38
+
### Resolve over-quota usage
39
+
40
+
If your experience exceeds your storage limits, you can:
41
+
42
+
-**Delete unused data stores.** If you're testing or have temporary stores, deleting them regularly helps maintain healthy storage usage. When you delete a data store, it can take Roblox up to 30 days to process your request.
43
+
-**Delete individual keys.** This is useful when you need to remove temporary items or a certain player's data.
44
+
-**Use the Batch Processor.** In cases when deleting data manually isn't efficient, you can use the Batch Processor or the Open Cloud Data Stores API to delete data in bulk.
45
+
46
+
### Use data store versions instead of new keys
47
+
48
+
When saving updates or new versions of player or configuration data, you can use the data stores versioning system instead of creating a new key for each version. Versioning allows you to roll back or inspect previous saves without increasing your total key count or storage footprint.
49
+
50
+
### Use memory stores for temporary data
51
+
52
+
Use [memory stores](../memory-stores/index.md) instead of data stores for caches or ephemeral data. The data in memory stores automatically expires after 45 days, which reduces your long-term storage growth.
53
+
54
+
### Clean up your data after testing
55
+
56
+
After you're done testing, delete test data stores through the Data Stores Manager. Avoid creating new scopes or entire new data stores just for test data.
57
+
58
+
### Store player data by key
59
+
60
+
Instead of storing player data by data store, store it by key. Deleting a key is faster than deleting a data store.
61
+
62
+
### Remove data after events
63
+
64
+
After seasonal events or temporary features, delete unused data through the Batch Processor or Open Cloud APIs.
65
+
66
+
### Review usage regularly
67
+
68
+
Make sure to review your usage regularly and detect anomalies early with the Data Stores Dashboard.
Copy file name to clipboardExpand all lines: content/en-us/cloud-services/data-stores/data-stores-manager.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,9 @@ To access the Data Stores Manager:
28
28
<br/>
29
29
<br/>
30
30
31
-
The **Summary** section of the Data Stores Manager page includes the **Total Size** and the **Storage Limit** of your data stores. The Total Size is calculated by adding the number of bytes consumed by all existing keys in your experience, and the Storage Limit is calculated based on your experience's lifetime user count. For more information about storage limits, see [Limits](./error-codes-and-limits.md#limits).
31
+
The **Summary** section of the Data Stores Manager page includes the **Total Size** and the **Storage Limit** of your data stores. Total Size is calculated by adding the number of bytes consumed by all existing keys in your experience, and Storage Limit is calculated based on your experience's lifetime user count. For more information about storage limits, see [Limits](./error-codes-and-limits.md#limits).
32
+
33
+
If your Total Size exceeds your Storage Limit, your **Est. Monthly Costs** will populate in your Summary and show an estimation of the impact of the usage that has gone over your quota. For tips on how to reduce your storage consumption, see [Best practices](./best-practices.md).
32
34
33
35
## View data stores and keys
34
36
@@ -41,10 +43,10 @@ The **Data Stores** list displays the name, size, and number of keys for all dat
41
43
To further drill down into each specific data store, you can:
42
44
43
45
- Select a data store from the data store list to display a list of all keys in that data store.
44
-
- Enter a prefix in the search bar to filter the list of keys.
45
-
- Toggle **Display scopes** to view the scope before each key name.
46
+
- Enter a prefix in the search bar to filter the list of keys. The prefix must start with the scope name.
46
47
- Select a key entry to display that key's value, metadata, version history, status, and when it was last updated.
47
-
- Select a key entry, select a version under **Version History**, and click **Compare Version** to compare the current key entry version with the version you selected.
48
+
- Select both a key entry and a version, and click **Compare versions** to compare the current key entry version with the version you selected.
49
+
- Select a previous version of a key and click **Revert** to go back to that version. You must have Edit permissions to do this. Reverting to a previous version conditionally updates the list and writes a new version with the value of the version you have previously selected.
48
50
49
51
<imgsrc="./../../assets/data/data-store/Data-Stores-Manager-Compare-Versions.png"alt="Comparison of two key entries in a data store." />
<td style={{border: 'none'}}><a href="https://create.roblox.com/docs/cloud-services/data-stores" style={{color: 'inherit', textDecoration: 'underline'}}><strong>Access to standard data stores</strong> (coming soon)</a></td>
130
+
</tr>
131
+
<tr>
132
+
<td style={{border: 'none'}}>Get</td>
133
+
<td style={{border: 'none'}}>250 + (CCU * 40) requests per minute</td>
<td style={{paddingBottom: '24px'}}>$0.12 / GB per Month</td>
119
181
</tr>
120
182
</tbody>
121
183
</table>
122
184
123
-
<figcaption>¹ GB Hours = the storage consumption multiplied by the amount of time. For example, 100GB Hours might equate to "100GB x 1 hour" or "200GB x 0.5 hours".</figcaption>
185
+
<figcaption>¹ GB per Hour = the storage consumption multiplied by the amount of time. For example, 100GB Hours might equate to "100GB x 1 hour" or "200GB x 0.5 hours".</figcaption>
186
+
187
+
## Supported countries
188
+
189
+
Extended Services is available in the following countries.
Copy file name to clipboardExpand all lines: content/en-us/production/monetization/game-passes.md
+37Lines changed: 37 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -201,6 +201,41 @@ end
201
201
Players.PlayerAdded:Connect(onPlayerAdded)
202
202
```
203
203
204
+
## Promote a pass
205
+
206
+
<Alertseverity="info">
207
+
Promoted passes are given to users for free.
208
+
</Alert>
209
+
210
+
To help more users discover your experience, you can opt-in to have your passes featured on Roblox's [Buy Robux](https://www.roblox.com/upgrades/robux) page. Opting-in to promote your passes can help increase the time and Robux users spend in your experience. There is no limit to the number of passes you can promote.
211
+
212
+
Users are shown passes that are relevant to their gameplay history and engagement on the platform. They are not shown passes that they already own.
![rbx-open-source-docs[bot]](https://avatars.githubusercontent.com/in/357490?v=4&size=40){kind=avatar}
0 commit comments