Skip to content
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

Performance problem (when printing a 7MB API endpoint on the REPL) #1281

Open
solanav opened this issue Jan 27, 2024 · 2 comments
Open

Performance problem (when printing a 7MB API endpoint on the REPL) #1281

solanav opened this issue Jan 27, 2024 · 2 comments

Comments

@solanav
Copy link

solanav commented Jan 27, 2024

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:

(ql:quickload :dexador)
(dexador:get "https://services.nvd.nist.gov/rest/json/cves/2.0?keywordSearch=Microsoft")

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!

@vindarel vindarel changed the title Performance problem Performance problem (when fetching a 7MB API endpoint on the REPL) Jan 27, 2024
@vindarel
Copy link
Collaborator

vindarel commented Jan 27, 2024

What brings the performance hit is printing the data. This works fine:

(setf *res* (dexador:get "https://services.nvd.nist.gov/rest/json/cves/2.0?keywordSearch=Microsoft"))

@vindarel 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
@solanav
Copy link
Author

solanav commented Jan 28, 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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants