Is there a maximum number of calls to the headless API before performance degrades?
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
legacy-article
learn-legacy-article-disclaimer-text
Issue
- Is there a maximum number of calls to the headless API before performance degrades?
Environment
- Liferay SaaS
- Liferay PaaS
Resolution
- We cannot specify a maximum number of calls that would avoid performance issues. However some guidelines can be provided to help understand the limitations:
If a script used to run headless API calls is single-threaded, the maximum upload latency will correspond to the largest file being uploaded. If it is multi-threaded to improve throughput, one should consider the number of threads configured on the server to ensure optimal performance.
Important note: file uploading itself is not CPU-bound; thus, the primary constraint is the upload latency for a single-threaded script. However, post-upload, there will be some CPU-bound tasks, such as adaptive media processing and preview generation. The extent of this CPU usage will depend on the specific files being uploaded, which will require additional analysis to understand fully.
did-this-article-resolve-your-issue