Windows explorer CPU usage going up while OpenBCI GUI is running

bmarkusbmarkus
in Software
Recently I've been plagued by artifacts in the Time series. They very much look like Github issues 231 and 349.

I have noticed at the same time that Windows explorer starts using 10-20% of my CPU while OpenBCI is running, this also happens even when all Windows explorer windows are closed. CPU usage of Windows explorer drops again to zero the moment that I close OpenBCI GUI. I've also used task manager to close Windows explorer while OpenBCI GUI is running, and that reduces the total CPU usage. 

Anyone else observe this behavior in Windows explorer? 

Comments

  • wjcroftwjcroft Mount Shasta, CA
    BMarkus, hi.

    Are you using the Wifi Shield? Are you using the Headplot in the GUI? I assume you read through those issue links.

    Mentioning @retiutut.

    There is a superior program for tracking Windows process resource utilization. It's called Process Explorer, from Microsoft.


    William

  • bmarkusbmarkus
    I'll try Process-explorer!

    Yes, I use Wifi shield, but never open the Headplot. Using the dongle is not an option for me as I need the higher sampling rate. 

  • retiututretiutut Louisiana, USA
    The GUI is not causing Windows Explorer to use the CPU. Tested on Windows 10 with Task Manager and VisualVM.
  • retiututretiutut Louisiana, USA
    • IMPORTANT: the WiFi shield is known to have reliability issues across different computer configurations. Using it effectively requires advanced technical skills and programming knowledge. Please proceed at your own risk. OpenBCI cannot guarantee that the device will work with your configuration. Have questions? Email [email protected]
  • bmarkusbmarkus
    Through process explorer I found out that windows defender get hyperactive within windows explorer. It is certainly related to the GUI though, because the increased activity starts and stops exactly with the GUI. 

    Maybe its time to switch to Ubuntu..
  • retiututretiutut Louisiana, USA
    edited May 2019
    The GUI really only causes the default file viewer to do something when we open/close files. Accessing the disk for files should be different than affecting how another program utilizes the CPU.
  • wjcroftwjcroft Mount Shasta, CA
    Might be that because the GUI / Hub are running as Administrator, Defender gets more defensive in it's monitoring.

    Are you saying that Defender dramatically increases CPU utilization? What figures do you see, for example Process Monitor will show you the percentages of cpu used by each process. And can sort that list with the highest priorities at the top.

    I'm not seeing this behavior with my Windows 7 here. But you have 10, much differences. Probably different Defenders also.
  • retiututretiutut Louisiana, USA
    ** and all of what @wjcroft just said
  • bmarkusbmarkus
    Screenshot 

    Windows explorer will fluctuate between 8-15% 

    During this screenshot I've got settings on UDP and 500Hz
  • bmarkusbmarkus
    also, my laptop is 4yr old Thinkpad with i7 and 16Gb
  • wjcroftwjcroft Mount Shasta, CA
    edited May 2019
    Here's a distinction you might not be aware of "WIndows Explorer", is the base desktop management app in the system. It not only performs file and folder explorer operations (when you open a folder window) -- it also drives the entire display in terms of receiving update notifications from other apps that are running on the screen.

    So while the GUI is doing frequent frame refreshing, the Windows Explorer is probably fielding events related to that. I'm guessing this explains the slight increase in Explorer CPU.

    As long as you have a reasonable amount of idle CPU, you are fine.
  • bmarkusbmarkus
    Ok so I'll stop worrying about it :) thanks for your help!
  • wjcroftwjcroft Mount Shasta, CA
    Are you using the UDPx3 radio protocol? 
  • bmarkusbmarkus
    Haven't tried it yet, need to install latest firmware first.
  • wjcroftwjcroft Mount Shasta, CA
    Highly recommended, it may well address your "I've been plagued by artifacts in the Time series".
  • bmarkusbmarkus
    I tried UDPx3 today, some trouble though.

    First I updated firmware on both the wifi shield and cyton. 

    Still not able to get UDPx3 to work though, after clicking 'start system' error message is that my wifi shield firmware is out of date.

    Am I missing something?

    Artifacts are near continuous, connecting in Wifi station mode and wifi direct, 500Hz UDP 10ms
  • retiututretiutut Louisiana, USA
    edited May 2019
    @bmarkus You have already mentioned https://github.com/OpenBCI/OpenBCI_GUI/issues/231. That's what's happening.

    Also, 

    • IMPORTANT: the WiFi shield is known to have reliability issues across different computer configurations. Using it effectively requires advanced technical skills and programming knowledge. Please proceed at your own risk. OpenBCI cannot guarantee that the device will work with your configuration. Have questions? Email [email protected]
  • bmarkusbmarkus
    @retiutut 

    I see issue 231 is there, so thats too bad for now, but that pertains to the artifacts, not to UDPx3 not working. 
    Regarding the disclaimer, I'll try some other laptops, and if that doesn't help I'll put my project on hold until 231 gets solved. 

    Any idea whats happening with future products being developed? I'm guessing we can expect something new as RFD22301 and Simblee are not available anymore, stock has to run out at some point.
  • retiututretiutut Louisiana, USA
    edited May 2019
    I'm not sure I can speak to the future of hardware development, since most of my contributions are software-related. I'm just here to let you know that the team is aware of issues with the WiFi shield, that's why we have added the disclaimer to the WiFi shield shop page. UDPx3 worked for me last year, and theoretically reduces packet loss. There have not been any changes to UDPx3, so it probably still works since I tested it last year. Again, all of this is hardware related, so UDPx3 is likely not broken.

    I think UDPx3 was supposed to be a big step up from TCP and UDP. Still didn't clean up **all** the artifacts and packet loss when connected to the Cyton or Cyton+Daisy.

    Ganglion+WiFi works for me, but it doesn't have the options to select UDP,TCP, or UDPx3.
  • bmarkusbmarkus
    I havent had any issues with Ganglion either, so for now I'll just work with that. 

    Thanks for support, I hope issues get resolved. 


  • retiututretiutut Louisiana, USA
    edited May 2019
    @bmarkus There's an issue with running Ganglion+WiFi at 1600hz and the updated Accelerometer Widget. No issues with 200Hz at the moment. That's the settings I recommend as of right now. If you want to stay up to date on these issues, head over to the Github and "watch" the issues you are interested in. Maybe even share "hey I have this issue also". Just trying to be transparent and open with the information that's available. Hope this helps!
  • bmarkusbmarkus
    I had noticed an issue at 1600Hz, but shrugged it off as my laptop needing replacement :) 
    As coding is not my thing I've only quietly lurked on Github, dont feel competent to chat with the big boys there. 

    I actually do have a widget for coherence under development that I'll share on Github soon, it needs some tweaks and maybe someone gets excited for it. 

    And yes, you are very helpful and I've experienced nothing but transparency in this community.
  • wjcroftwjcroft Mount Shasta, CA
    @bmarkus and @retiutut, thanks.

    I just posted on the issue page regarding a potential workaround / solution. Your opinions there would be appreciated.

Sign In or Register to comment.

© Vanilla Keystone Theme 2026