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
We haven't been putting directed focus on measuring and improving performance of Wasp apps, regards how much resources is consumed during development but also in production, size of apps, speed of dev cycle, speed of data flow and page loads, ... .
We have been keeping all of those in an ok shape of course, but for 1.0, we will want to do a focused study, do proper measurements and evaluate exactly in which shape are we, and then make a plan on how to make improvements.
As part of this effort, we should also put into place automatic tests/checks (in the CI) that will ensure performance is maintained at the level we want, and we can then keep raising that level with time.
We will also want to enrich documentation with the information on what users can do on their side to achieve the best performance out of Wasp apps.
The text was updated successfully, but these errors were encountered:
Perhaps a page like Wasp in Production may help with some general performence reports of server and client.
Indeed, it might be valuable to have a dedicated page that talks about what a user can expect from running Wasp in Production -> scaling, performance, security, all of it. This could be an umbrella page, and then we can dive into specific topics further, in the docs.
We haven't been putting directed focus on measuring and improving performance of Wasp apps, regards how much resources is consumed during development but also in production, size of apps, speed of dev cycle, speed of data flow and page loads, ... .
We have been keeping all of those in an ok shape of course, but for 1.0, we will want to do a focused study, do proper measurements and evaluate exactly in which shape are we, and then make a plan on how to make improvements.
As part of this effort, we should also put into place automatic tests/checks (in the CI) that will ensure performance is maintained at the level we want, and we can then keep raising that level with time.
We will also want to enrich documentation with the information on what users can do on their side to achieve the best performance out of Wasp apps.
The text was updated successfully, but these errors were encountered: