Every time your app stores or retrieves some data, that’s a request. We start you out with 30 requests every second (that’s 1,800 a minute), which will cover a pretty large amount of traffic.
Need to scale? No problem — you can change your plan at any time, up to a maximum of 600 requests/second. We only bill you by the hour.
The requests/second limit is per-app and is calculated on a per-minute basis. For example, if an app is set to 30 requests/second, your app will start hitting its request limit once it generates more than 1,800 requests in a 60 second period. You can see how many requests per second each app is sending to Parse by loading the Performance graph in the Analytics section of your dashboard.
Once your app exceeds the request limit, any further requests will be dropped until the average number of requests sent over a trailing 60 second window drops under the request limit for this app. To prevent the requests from failing you should adjust your request limit for the relevant app on the App Settings page in the dashboard.
Every app is different and the answer will depend on how efficient the app is in terms of request usage as well as your user's behavior patterns. We estimate that the average app's active user will issue 10 requests. Thus, if this app's traffic was evenly spread throughout the day, it would be able to handle around 250,000 daily active users under the free tier. Every app is different, so we strongly encourage you to measure how many requests your users send on average.
You can find the number of daily active users in your Analytics overview graph in the dashboard. The number of requests your app is consuming per second can be found under Performance. Consulting these two figures should help you arrive at an estimate of how many requests per second the average user will send your way. If you're expecting a serious amount of traffic, we recommend setting up a beta program with a few dozen users prior to launching your app publicly. This will help you get a better estimate of how your app performs with a wider variety of users, and in turn it will help you plan ahead for your big marketing launch.
What happens if I increase my request limit and my app does not exceed this limit?
When you increase your request limit, you're provisioning additional capacity ahead of time. Your account will be billed according to the request limit that has been set, regardless of how many requests your app actually made.
Parse will not adjust any app's request limit automatically. We recommend setting the request limit high enough to support the amount of traffic generated by your app on average.
Queries, saves, logins, amongst other kinds of operations will be taken into account when determining the number of requests generated by your app. A request to send a push notification sent by a SDK will count as a single request regardless of how many installations are targeted. Batched requests will be counted based on the number of operations performed in each batch. Serving Parse files counts as an API request, including static assets served from Parse Hosting. Analytics requests do not count towards your app's request limit.
Background Jobs allow you to set up long running tasks that can be run on demand or on a schedule.
If you schedule more concurrent background jobs than your app is provisioned for, the scheduling API will return an error indicating that you are out of capacity. Apps may have one job running concurrently per 20 req/s in their request limit. You can control the number of concurrent background jobs for each of your apps by adjusting the request limit slider on the Account Overview page. In general, if you need more concurrent jobs, you are likely to also need more requests per second capacity.
Database storage refers to data stored as Parse Objects, which are limited to 128 KB in size. File storage refers to static assets that are stored using the Parse File APIs, typically images, documents, and other types of binary data.
You will find everything you need in the Performance view within the Analytics section of your Parse Dashboard. The amount of File Storage, Database Storage, and Data Transfer currently used by an app will be displayed below the graph, under Billing data.
What happens if my app exceeds the limits for file storage, file transfer, or monthly uniques (push notifications)?
The numbers you see on our pricing page for File Storage, File Transfer, and Push Notifications are soft quotas that can be exceeded without running into any errors or service interruptions. Any overages will be reflected in your next Parse bill.
The overage rate for database size is $10/GB but we only allow increases in increments of 20 GB. When you you exceed 20 GB of database size we will increase your soft quota to 40 GB and begin charging you an incremental $200/month. When you hit your new soft quota of 40 GB we will increase your soft quota to 60 GB... and so on up to a hard limit of 100 GB.
Large files can present a problem on mobile devices with tight memory constraints. Parse's File Storage API has a 10 MB per-file hard limit which cannot be increased. If you need to store more than 10 MB in an individual file, you have several options: host the file as a static asset using Parse Hosting, split the larger file into 10 MB chunks and reconstruct on the client, or use a third party file storage provider to store the file.
Parse does not support request limits over 600. We highly recommend going through the Performance Guide and watching our Building Apps at Scale video session to ensure that you are making the most efficient use of Parse. In practice, very few apps will require a request limit above 600.