I am profiling a cuda application on different 1d input sizes. However NSIGHT profiler kernel execution times are similar for small vector sizes. As an example, there is not any difference between vector sizes 512 and 2048.Kernel execution time increases linearly for bigger vectors but no difference on smaller vectors like vector size 512 and 2048. Is it an expected result?
CUDA Kernel Execution Time does not change on larger array
176 Views Asked by Joel Willingar At
1
There are 1 best solutions below
Related Questions in CUDA
- Angular Show All When No Filter Is Supplied
- Why does a function show up as not defined
- I count the time the user takes to solve my quiz using Javascript but I want the same time displayed on another page
- Set "More" "Less" font size
- Using pagination on a table in AngularJS
- How to sort these using Javascript or Jquery Most effectively
- how to fill out the table with next values in array with one button
- State with different subviews
- Ajax jQuery firing multiple time display event for the same result
- Getting and passing MVC Model data to AngularJS controller
Related Questions in NSIGHT
- Angular Show All When No Filter Is Supplied
- Why does a function show up as not defined
- I count the time the user takes to solve my quiz using Javascript but I want the same time displayed on another page
- Set "More" "Less" font size
- Using pagination on a table in AngularJS
- How to sort these using Javascript or Jquery Most effectively
- how to fill out the table with next values in array with one button
- State with different subviews
- Ajax jQuery firing multiple time display event for the same result
- Getting and passing MVC Model data to AngularJS controller
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
Let's suppose it takes 3 microseconds of execution time to launch a kernel of any size, and, after that overhead, 1 ns of execution time per point in your vector. Now let's ask, what is the percent difference in the execution of kernels of
x
and2x
points, whenx
is small (say 1024) and whenx
is large (say, 1048576)?x
= 1024:x
= 1048576:This demonstrates what to expect when making measurements of execution time (and changes in execution time) when the execution time is small compared to the fixed overhead, vs. when it is large compared to the fixed overhead.
In the small case, the execution time is "swamped" by the overhead. Doubling the "work" does not lead to a doubling in the execution time. In the large case, the overhead is insignificant compared to the execution time. Therefore in the large case we see approximately the expected result, that doubling the "work" (vector length) approximately doubles the execution time.
Note that the "fixed overhead" here may be composed of a number of items, the "kernel launch overhead" being just one. CUDA typically has other start-up fixed "overheads" associated with initialization, that also play a role.