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

Suave.Json.toJson allocates ~22MB on the large object heap #324

Closed
cartermp opened this issue Jan 11, 2019 · 7 comments
Closed

Suave.Json.toJson allocates ~22MB on the large object heap #324

cartermp opened this issue Jan 11, 2019 · 7 comments
Labels

Comments

@cartermp
Copy link
Contributor

  • Open FSAC solution
  • Open some files
  • Edit some functions that use FCS types

image

Not an incredible amount, but over a long period of time this may pile on and lead to noticeable GC pauses (which will halt the FSAC process).

@cartermp
Copy link
Contributor Author

It may be better to hold off on anything related to this until at least after #320 is merged.

@7sharp9
Copy link
Contributor

7sharp9 commented Feb 13, 2019

I would love to know whats in here:
screen shot 2019-02-13 at 12 25 25

@cartermp
Copy link
Contributor Author

#323 is likely much more of a contributor to the working set memory usage than this. But this is LOH allocations which means that over time it will cause the GC to pause all threads when it collects. That need not happen at high memory usage levels either.

@7sharp9
Copy link
Contributor

7sharp9 commented Feb 13, 2019

In my instance I saw a sawtooth graph of allocation with cpu spikes at GC I guess. At this point I have tor restart as its no longer responsive.

@cartermp
Copy link
Contributor Author

Without profiling things it's unclear what the issue is. But I don't think this is the problem, otherwise it would have shown up in my own profiling.

@7sharp9
Copy link
Contributor

7sharp9 commented Feb 13, 2019

Yep of course, In this instance it was opening falanx and opening half a dozen files

@cartermp
Copy link
Contributor Author

Closing this as outdated now that LSP support is in.

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

No branches or pull requests

3 participants