Recommended Posts

Just a word of warning to anyone else who deploys this -- it is very heavy on the CPU and we had to disable for now until we can review the code to see how (if at all) this can be optimized.  The results are awesome, but so far our observation has been otherwise healthy collectors are brought to their knees.

Share this post


Link to post
Share on other sites
On 2/18/2019 at 4:04 PM, mnagel said:

Just a word of warning to anyone else who deploys this -- it is very heavy on the CPU and we had to disable for now until we can review the code to see how (if at all) this can be optimized.  The results are awesome, but so far our observation has been otherwise healthy collectors are brought to their knees.

@mnagel - Was this still being experienced with updated collectors?

I have deployed this datasource to a few of our systems and will report back on our findings.

Share this post


Link to post
Share on other sites

@WillFulmer I have not tried again since then -- did not seem to be a collector issue, more that the Powershell involved was too intense.  Worked fine in a few cases, but when the server count was in the 80+ range (which is no problem normally), the collector bogged down and lost data until we disabled it.  I have not had a chance to go over the code too much to see how it could be made more efficient.  It may not be possible...

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now