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

100% CPU core with ofxUDPManager set at non-blocking #36

Open
artificiel opened this issue Nov 7, 2022 · 0 comments
Open

100% CPU core with ofxUDPManager set at non-blocking #36

artificiel opened this issue Nov 7, 2022 · 0 comments

Comments

@artificiel
Copy link

An application receiving ofxArtnet will consume 100% of a CPU core just waiting for the data (on a Mac M1, it means about 200000 loops per seconds of the threadedFunction() . In ofxArtnetReceiver::setup() changing settings.blocking to false drops the % to ~5%.

I don't mind preparing a pull request but I don't know what the default should be (I personally don't see a latency issue with blocking enabled so I use that) but either change the default and/or add a method or setup parameter to specify blocking?

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

1 participant