Rate Limits in Adobe IO Runtime

In Adobe I/O Runtime, rate limits are based on namespace rather than on a workspace. Each namespace is associated with its own set of rate limits for invocations and other usage, such as concurrent executions.

This means that if you have multiple actions deployed under the same namespace, they will share the rate limits for that namespace. Workspaces are primarily used to organize and manage your projects and actions but do not have a direct impact on the rate limits.

To summarize:

• Rate limits are based on the namespace.
• Actions in the same namespace share the rate limit.

If you require higher limits, you can explore options for requesting increased rate limits via Adobe support, or you may consider organizing actions into different namespaces if that suits your needs.

Exactly as Amanath shows, default rate limits are as per 

 https://developer.adobe.com/runtime/docs/guides/using/system_settings/

But we get liberty to extend default limits (again within adobe defined max limits) using limits field in app.config.yaml. Refer runtime manifest here 

https://developer.adobe.com/app-builder/docs/guides/configuration/#runtime-manifest

you can change timeout, concurrency, memory, all default values can be edited.