-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
How to start local development? #18
Comments
If you want to start development with a complete working app as a template, an easy way is to download the contents of this repository and use the example app from
(You can use the |
Thanks for the answer! |
Yes, it works for online stores and blogs. Fifty thousand items are within the supported limits. But another metric to consider is the size of your database. At the moment (with the current implementation), the size of the database is limited to a few hundred MB. For online stores, you often have images taking up quite some space. Usually, the app does not need to read the contents of these images. It is enough to link to them as static external files. Then you can host them outside the Elm app to avoid them blowing up the Elm database size. |
Thanks for the answer |
I will run a test to measure the exact limits of today's implementation. |
Add an example app to support interactive testing of the database limits, as discussed at #18
I ran a test and found another important limit for total app state size: App state sizes of more than 166.6 MB will usually crash the server with v2022-03-20. Therefore elm-fs is not currently fit for that workload. Restarting a server with v2022-03-20 crashed with this exception:
It crashes because the current implementation depends on a limit similar to the one discussed at: dotnet/runtime#39953 In our case, it should be |
Oh thanks for the replies! |
Avoid the size limit for the application state discovered at #18: Instead of packaging the JSON in a string, use the JSON directly on the interface to transport to the JS engine. For further discussion of the serializer limit in System.Text.Json, see dotnet/runtime#39953 and dotnet/runtime#61089
Hi!
The text was updated successfully, but these errors were encountered: