I have currently upgraded to OpenCLSDK v19.3 and found that the legacy emulator is much slower than previous versions. I am using the same OpenCL code with the same compilation configurations.
Is there any new changes in this new version ?
I had compare the both version in getting start guide. I saw that the memory requirement and RAM requirement are the same.
Sometimes with newer versions, it might requires higher computer specs.
Compilation to the same design files with slower time, there might be some computer spec performance issues. Firewall / antivirus might also affect the performance.
You may need to monitor the memory usage while run compilation to check the consumption by the tool.
Soft reminder: Changes of OpenCL SDK v19.3 can be found here:
Hi thanks for the reply.
I just releaized that I am using the lagecy emulator for SDK v18.1 and v19.1 and the new "fast" emulator for v19.3. Because they have changed the compilation options for v19.3 (you have to explicitly specify -legacy-emulator to use the old legacy emulator). So my observation is that the new emulator is running much slower during emulation (not during compilation) than the old legacy one.
Hi, I still could not make the legacy emulator work for v19.3 SDK. After I added the "-legacy-emulator" option and recompiled the kernel file, the host executable returns an error showing that "incorrect aocx files", I am not sure what I have missed in order to launch the legacy emulator for v19.3 ?
PS. It is all about execution time of the simulation rather than compilation time.
Thx for your reply again. I can not share with you the code publicly, but I could invite you to our private repo on github to access all the code. Do you mind sending me your github acount ID so I could send you an invitation link.
May I know the information as below for confirmation:
eg: aoc march=emulator-legacy-emulator
Hi, I can confirm the boardtest.cl and the example works fine for the emulator as the following log shows:
Platform: Intel(R) FPGA Emulation Platform for OpenCL(TM)
Using 1 device(s)
Intel(R) FPGA Emulation Device
Using AOCX: vector_add.aocx
Launching for device 0 (1000000 elements)
Time: 4.284 ms
Kernel time (device 0): 1.197 ms
I am fully aware of the new ENV for v19.3 and the variable was correctly set.
The official examples provided are too small that only execute for a few seconds that makes the performance difference between the two emulators unnoticable.
You could use our opensource project PipeCNN (https://github.com/doonny/PipeCNN) to test the emulator, please try to run VGG16/ResNet-50 benchmarks and you will see the difference in emulator execution time between v19.1 and v19.3.
Our inhourse project has a much bigger longer runtime when using the new emulator. The project uses several autorun kernels, I susbect the autorun kernels caused this problem. I have captured the CPU utilization as follow. You can clear see there is a big difference: the legacy emualtor uses more threads compared to the new one.
2. emulator v19.1 (lagecy one)
I am using Ubuntu 16.04.6 (Linux fpga-z390 4.15.0-72-generic #81~16.04.1-Ubuntu SMP Tue Nov 26 16:34:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
on a i9-9900K CPU with 64GB memory.
I had download the file and looking into the file.
I saw many .cl file in project/device file.
May I know which file you want to compile at my side? Or do I need to compile all the file?
Hi , sorry for the late response, please re-download the project from this link: https://drive.google.com/open?id=10l0pjMVIvUSwGTT7DrFam7qRcTdcGHm1
pwd for the zip file is 611611,
I have wrote detailed instructions on how to run the emulations in a README file. Thanks for your time.
I had followed the instruction but there is an error occurred as below:
host/main.cpp:25:22: fatal error: ocl_util.h: No such file or directory
I had recheck back the the script of makefile in root folder, there is include two file:
I did not found the "common" folder.
Using AOCX: traffic_stn.aocx
Context callback: clCreateProgramWithBinary failed
Failed to create program with binary
I am getting this error with -legacy emulator , please help me