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

Timer problem in CEDD #14

Open
gpdavila opened this issue Aug 2, 2017 · 2 comments
Open

Timer problem in CEDD #14

gpdavila opened this issue Aug 2, 2017 · 2 comments

Comments

@gpdavila
Copy link

gpdavila commented Aug 2, 2017

Hello everybody.
I'm executing CEDD with default configuration and the output seem really strange.
Randomly it gets an enormous number.

CEDD output

Spectre -p 0 -d 0 -i 16 -a 0.20 -t 4
Allocation Time (ms): 0.071000
Initialization Time (ms): 2532.493000
Total Proxies Time (ms): 436.893000
CPU Proxy:
CPU Proxy: Kernel Time (ms): 432.369000
GPU Proxy:
GPU Proxy: Copy To Device Time (ms): 1501703139477.527100
GPU Proxy: Kernel Time (ms): 58.478000
GPU Proxy: Copy Back Time (ms): 9.976000
Deallocation Time (ms): 8.021000
Test Passed

Spectre -p 0 -d 0 -i 16 -a 0.20 -t 4
Allocation Time (ms): 0.073000
Initialization Time (ms): 2583.880000
Total Proxies Time (ms): 427.340000
CPU Proxy:
CPU Proxy: Kernel Time (ms): 1501703148589.305908
GPU Proxy:
GPU Proxy: Copy To Device Time (ms): 11.677000
GPU Proxy: Kernel Time (ms): 54.310000
GPU Proxy: Copy Back Time (ms): 9.947000
Deallocation Time (ms): 8.555000
Test Passed

I also executed BS and this never happened.
Do you have an idea of the reason of this?

Gabriel

@el1goluj
Copy link
Member

el1goluj commented Aug 4, 2017

This is a known issue. We are working to fix it. We will get back to you as soon as possible. Meanwhile, you can do your measurements with several runs, since the error appears infrequently, as fas as I know.

Juan

@el1goluj
Copy link
Member

el1goluj commented Aug 28, 2017

Hi Gabriel,

We have found the problem with CEDD timing. The bug is a race condition on the timer between the two proxy threads. It will be fixed shortly.
One quick way to fix it is using different timers for CPU and GPU proxy threads. You may want to do it yourself, before we release the fix.

Juan

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

2 participants