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

How much GarbageCollectionCachePruner instances should we have in a runtime for a healthy app? #242

Closed
SychevIgor opened this issue May 31, 2017 · 1 comment

Comments

@SychevIgor
Copy link

Hi,
I need an advise, how much instances of GarbageCollectionCachePruner we should have in a memory for a windows service app?

I have 244000( 244 thousands) objects in an app, and something telling me that it's not normal.

image
Based on my research it's a root cause of high cpu utilization, because we also have 245k timers in memory and each timer throwing event every 30 second...
I think it's because something preventing timer from GC...

I need only an answer- how much GarbageCollectionCachePruner objects should be in an app and if we have some guides about normal number of loggers in a Ninject container(but it's optional)...

@scott-xu
Copy link
Member

scott-xu commented Jun 3, 2017

Should be only one

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