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
I consult the following API for example: nist CVE API. The result is 7.7MB aprox. Lem gets stuck for ~10s, then it shows the result and continues to use 100% of a core and becomes unresponsive.
Maybe this is out of the current objectives of the project but its annoying having to restart Lem. And because the REPL is made to develop exploring, I don't want to be careful not to break it. If there is anything I can do to help I'd love to. Thanks!
The text was updated successfully, but these errors were encountered:
vindarel
changed the title
Performance problem
Performance problem (when fetching a 7MB API endpoint on the REPL)
Jan 27, 2024
vindarel
changed the title
Performance problem (when fetching a 7MB API endpoint on the REPL)
Performance problem (when printing a 7MB API endpoint on the REPL)
Jan 27, 2024
Could this be similar to Emacs' performance problem with long single lines? And is it within the scope of the project to make it perform better with big text?
I consult the following API for example: nist CVE API. The result is 7.7MB aprox. Lem gets stuck for ~10s, then it shows the result and continues to use 100% of a core and becomes unresponsive.
To reproduce:
Maybe this is out of the current objectives of the project but its annoying having to restart Lem. And because the REPL is made to develop exploring, I don't want to be careful not to break it. If there is anything I can do to help I'd love to. Thanks!
The text was updated successfully, but these errors were encountered: