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

Quick fix for high network use with large operation sets #52

Closed
wants to merge 1 commit into from

Conversation

timbrigham-oc
Copy link
Contributor

This is a quick fix for #51 in open requests.

Not a fix for the underlying issue, but it makes the console way more responsive.

@elegantmoose
Copy link
Collaborator

@timbrigham-oc So changing to an int did have noticeable effect?

@timbrigham-oc
Copy link
Contributor Author

@elegantmoose, unfortunately not. I did some digging, apparently that scheduler is supposed to cast strings into ints if required. I thought it was firing every second, but when I hit it with a stopwatch it was every 3 as configured. It was still was enough to ramp my machine upto over a hundred mbps when on this screen however.

@elegantmoose
Copy link
Collaborator

Oh, you increased the value. Sorry, missed that.

@timbrigham-oc
Copy link
Contributor Author

This shouldn't be needed with #53, just a workaround until it could be applied.

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

Successfully merging this pull request may close these issues.

2 participants