CVI Execution Profiler - DLL overhead

Question

Hello,
I'm using CVI execution profiler toolkit to analyze performance in system where a implicity linked DLL is called from an application exe.
It appears that in many of the statistics the component time % for the exported DLL function is roughly half the overall time for the component.
For example (with 'dll_function' selected in profiler):
+exe_function
-dll_function                         50%
DebugPrintf                48%
OtherFunction              2%
Would this time coorelate with overhead of calling the DLL?
Thank you for any help in regards to this.
Solved!
Go to Solution.

Answer 1

Hey jharris,
I ran one of our simple examples and saw somewhat similar behavior--my GetUserEvent function takes about 66% of the time and the DLL function takes 33%. In my case, this simply means that the code is spending more of its time running the GetUserEvent function than in the DLL function. I'd expect this, since the GetUserEvent function is checking for UI updates. 
Is your exe function doing something other than just calling the DLL function, and do you see the other 50% of time anywhere else in the execution profile? If so, I suspect that it's just indicating that only half of your execution time is spent in the DLL function.
Daniel E.
TestStand Product Support Engineer
National Instruments