29
edits
Changes
→Christopher Ginac Image Processing Library
It seems most of our time in this part of the code is spent assigning our enlarged image to the now one, and also creating our image object in the first place. I think if we were to somehow use a GPU for this process, we would see an decrease in run-time for this part of the library. Also, there also seems to be room for improvement on the very 'Image::enlargeImage' function itself. I feel like by loading said functionality onto thje GPU, we can reduce it's 0.76s to something even lower.
Using the same image as above (16MB file), I went ahead and profile the Negate option as well. This as the name implies turns the image into a negative form.
<pre>
real 0m5.707s
user 0m0.000s
sys 0m0.000s
</pre>
As you can see, about half the time of the Enlarge option, which is expect considering you're not doing as much.
<pre>
Flat profile:
Each sample counts as 0.01 seconds.
% cumulative self self total
time seconds seconds calls ms/call ms/call name
23.53 0.16 0.16 2 80.00 80.00 Image::Image(Image const&)
16.18 0.27 0.11 2 55.00 55.00 Image::Image(int, int, int)
14.71 0.37 0.10 _fu62___ZSt4cout
13.24 0.46 0.09 17117346 0.00 0.00 Image::getPixelVal(int, int)
13.24 0.55 0.09 1 90.00 90.00 Image::operator=(Image const&)
7.35 0.60 0.05 1 50.00 140.00 writeImage(char*, Image&)
7.35 0.65 0.05 1 50.00 195.00 Image::negateImage(Image&)
4.41 0.68 0.03 17117346 0.00 0.00 Image::setPixelVal(int, int, int)
0.00 0.68 0.00 4 0.00 0.00 Image::~Image()
0.00 0.68 0.00 3 0.00 0.00 std::operator|(std::_Ios_Openmode, std::_Ios_Openmode)
0.00 0.68 0.00 1 0.00 0.00 readImageHeader(char*, int&, int&, int&, bool&)
0.00 0.68 0.00 1 0.00 0.00 readImage(char*, Image&)
0.00 0.68 0.00 1 0.00 0.00 Image::getImageInfo(int&, int&, int&)
</pre>
Notice in both cases of the Enlarge and Negate options the function "Image::Image(int, int, int)" is always within the top 3 of functions that seem to take the most time. Also, the functions "Image::setPixelVal(int, int, int)" and
"Image::getPixelVal(int, int)" are called very often. I think if we focus our efforts on unloading the "Image::getPixelVal(int, int)" and "Image::setPixelVal(int, int, int)" functions onto the GPU as I imagine they are VERY repetitive tasks, as well as try and optimize the "Image::Image(int, int, int)" function; we are sure to see an increase in performance for this program.
==== Merge Sort Algorithm ====