-
Notifications
You must be signed in to change notification settings - Fork 584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improving ApostropheCMS Performance with High Request Volumes and Large JSON Payloads #4462
Comments
Hi maamounkhlifi, My first concern would be to prove it's definitely about the size of those JSON payloads. One way to do that is to use Also, what does your CPU load look like in this situation? Are you running multiple servers with a load balancer or is all of this traffic being served by a single process? Also a good idea to check the CPU load on your mongodb server or cluster. If you'd like to talk about having a full performance analysis of your application done by the Apostrophe development team, please do reach out to us and let the team know I sent you: |
We're currently experiencing performance challenges with our ApostropheCMS application, particularly when handling around 500-600 requests per minute (Rest API). The primary issue seems to stem from the transfer of large JSON payloads, as our models are complex, featuring numerous widgets and mixed relations.
Despite leveraging projection to trim down the data size, we're still facing slower response times than desired. This is especially true for data returned from widgets, such as the
apostrophecms/image
widget, where we ideally want to retrieve only theoriginalUrl
instead of the entire object.I'm looking for advice on the following:
apostrophecms/image
, is there a way to limit the returned data to only essential information, such asoriginalUrl
?Any insights or suggestions on improving ApostropheCMS performance in such scenarios would be greatly appreciated.
The text was updated successfully, but these errors were encountered: