-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Delimiter parser High CPU usage #1329
Comments
I'm willing to bet this is due to the recently closed windows write issue #1221 if you try with the latest 6.0.0 beta you might see an improvement. We'll release 6.0 once that has more testing. Thanks! |
I can confirm that after testing with |
We need more people testing first. It's a big change! A week or two
probably.
…---
Francis Gulotta
[email protected]
On Fri, Sep 8, 2017 at 10:40 AM, Jan Koutný ***@***.***> wrote:
I can confirm that after testing with 6.0.0-beta2 the usage dropped to
around 0-1%!🎉
When can I expect rolling out 6.0.0 to npm?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1329 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABlbhoser3Qr1g_JYGaPvxHI2oF_jauks5sgVHOgaJpZM4PPzZ_>
.
|
OK. Thanks. |
Keep using it and report any any issues you might have =) I think @dustmop would be happy to know of your success. =) |
SerialPort Version: 5.0.0
NodeJS Version: v6.11.1
Operating System and Hardware Platform: Windows 10, x64
Have you checked the right version of the api docs?: yes
Are you having trouble installing and you checked the Installation Special Cases docs? no
Are you using Electron and have you checked the Electron Docs?: no
Summary of Problem
When I run this code:
The Node.js process consumes about 30-40% of CPU. When I comment out construction of the parser, usage is around 1%. I first noticed this using serialport in electron, but it's the same in Node.
The device is not sending any data to the port, and the usage doesn't drop even after physically unplugging the cable.
Steps and Code to Reproduce the Issue
Just run the code above.
The text was updated successfully, but these errors were encountered: