Home › Forums › Eye Tracking Devices › CPU-Consuming Problem
Tagged: Tobii EyeX Controller
- This topic has 4 replies, 2 voices, and was last updated 8 years, 9 months ago by huangteng.
- 04/06/2014 at 14:52 #1099
For a competition, I have to use the EyeX Controller on an Intel BayTrail board with CPU Clock Speed 1.33GHz and working on 64b win8.1 system. I know that it cannot satisfy the recommended requirments, but it can work on this board for the most time. While, somehow CPU will be overloaded and EyeX will stop working with lights off. So I am wondering if there is a way to get a lower CPU-consuming Eyex Engine or other ways to solve this problem.04/06/2014 at 16:02 #1101Jenny [Tobii]Participant
We are actively and continously working on making the EyeX Engine CPU load as low as possible. You could expect improvements in future releases.
In this particular case, though, it might be a problem with the EyeX Controller firmware. Which Tobii EyeX Controller Server version do you have installed? The latest available version is 0.9.7.04/06/2014 at 16:37 #1102
I have confirmed that our software is the latest releases, in which USB version 18.104.22.168, Controller Driver version is 0.9.3, Controller Service version is 0.9.7 and EyeX version is 0.8.16.811.
In our case, I only tested the performance using the program in EyeX SDK which is based on the EyeX Engine. And I saw the EyeX Setting Panel , EyeX Engine and EyeX for Windows occupied the most resources of CPU. According to your SDK’s descriptions, will GazeSDK use the processes I listed above? If not,could it be true that I would get better performance and have my problem above solved, if I consider using GazeSDK which implement the function of EyeX at low_level?05/06/2014 at 12:34 #1111Jenny [Tobii]Participant
Ok, then we can exclude the firmware from being the problem.
The EyeX Settings Panel will only use CPU when it is open, so you could keep that closed to save a little on the load.
The EyeX for Windows is a separate application and process and could also be shut down. At the present you do it manually by ending the task in the task manager, but in the next EyeX software release we have made it easier to close EyeX for Windows and only run the EyeX Engine from computer startup.
Also, in the next EyeX release, further enhancement on the engine performance is included. This release is currently being finalized and is expected to be publicized now in june.
Please, try running with the EyeX Engine only by stopping the other two processes and see if you get a feasible CPU load.
If you don’t, then the Gaze SDK would be an alternative since it does not use the engine. But it does, however mean that you would have to set up the screen plane and calibration yourself, and do all filtering of the raw data streams yourself.06/06/2014 at 13:56 #1117
Thanks for your patience.
The program I’m using was modified from “MinimalGazeDataStream” in the EyeXSDK’s sample.And I have tried to shut down the two processes you mentioned above with task manager. But they automatically start every time I run my program. What should I do with the code in order to keep these processes from starting with my program ?
- You must be logged in to reply to this topic.