-
Notifications
You must be signed in to change notification settings - Fork 164
I get the ~same FPS by using -numncs 1 and -numncs 2 #49
Comments
@AlexeyAB (1) Python script (2) C++ script OpenVINO 2019 R2 was released the other day. Multi-stick API level support and the ability to measure the stick's internal temperature have been added. I will update YoloV3's repository to correspond to the latest API after a while. |
@PINTO0309 Hi,
|
Hi, @AlexeyAB My Python program is waiting for 7 seconds to initialize one NCS2. In other words, the first NCS2 takes effect after 7 seconds and the second NCS2 takes effect after 14 seconds. Is the performance the same even if you wait 14 seconds? Hmmm... I do not know where the bottleneck is... |
@PINTO0309 Yes, even if I wait 60 seconds, FPS is the same. |
I have the same problem too :( |
I should get 2x more FPS by using -numncs, isn't it?
[Required] Custom device Atom CPU + 2 x MyriadX (VPU) via mini-PCI-express
[Required] Your device's CPU architecture x86_64 Intel Atom E3845
[Required] Ubuntu16.04.6 LTS (OpenVINO 2019.1.144)
[Required] Details of the work you did before the problem occurred:
I get the ~same FPS by using
-numncs 1
and-numncs 2
.I get
![image](https://user-images.githubusercontent.com/4096485/60817086-a87cc080-a1a3-11e9-8000-ab7b2cf14a00.png)
10.7 FPS
by using-numncs 1
And I get
![image](https://user-images.githubusercontent.com/4096485/60817111-b5011900-a1a3-11e9-99c0-8e828238ee82.png)
10.3 FPS
by using-numncs 2
By running
![image](https://user-images.githubusercontent.com/4096485/60817273-04474980-a1a4-11e9-8bf6-89b8bc0aca66.png)
multistick_cpp
example from OpenVINO, I get this message:The text was updated successfully, but these errors were encountered: