-
Notifications
You must be signed in to change notification settings - Fork 0
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
HTML UI Lambda memory usage #23
Comments
2022-02-01 updateIt is kind of tolerable.
There is a discussion in serde-rs/json#635 regarding this same problem and a potential solution in https://github.com/Diggsey/ijson crate. It is not known if it will work with Tera. @Diggsey thinks it might (Diggsey/ijson#6). Alternative solutions:
None of the above is a quick fix for the problem. |
Looks like Tera adds a significant overhead as well. This example includes double conversion: ES -> String -> struct Report -> Value.
In this test where ES data is converted straight into Value there is no much memory use by Tera:
|
* no idea where that filter line came from and why - it works in PROD as-is * removed the line to make it work, not sure what else is affected
Too many HTML UI Lambda requests fail because serde uses too much RAM deserializing into Value.
Examples:
A potential solution can be converting into a struct first and then convert into Value. I do not know if it will produce a smaller object.
512MB results in <10% failure rate, but given that lists are larger than dev profiles it would be search results pages that fail the most.
The text was updated successfully, but these errors were encountered: