SCM

Discussion Forums: help

Monitor Forum | Start New Thread Start New Thread

 

RE: slow-down in the opening of many images [ reply ]
By: Aurélien Jaffard on 2016-03-30 13:30
[forum:3595]
Hello all,

After working on this with the camiTK Team,

We found a few things:

1) When targeting performance, it is better to use directly the constructor of specific component rather than Application::Open()
in given code, it is quicker to use new VtkImageComponent(file) rather than Application::Open(file)

for info with only this modification & for opening 1000 images
Average time for 100 firsts : 4.56 ms
Average time for 100 lasts : 118.84 ms
Average time for all : 48.952 ms
Total time : 48.952 s

2) The camiTK team has also made optimizations on refresh and a few other things.
it will be available on the git as soon as it becomes public

for the pleasure with this optimizations & for opening 1000 images
Average time for 100 firsts : 2.86 ms
Average time for 100 lasts : 6.22 ms
Average time for all : 5.239 ms
Total time : 5.239 s

For all this help &
To all the camiTK Team (and especially Mahnu)
Thank you


RE: slow-down in the opening of many images [ reply ]
By: Aurélien Jaffard on 2016-03-14 09:46
[forum:3565]

test.txt (47) downloads
hello Mahnu

first of all,
sorry for the compatibility, i will use QTime next time.

for my test :
- image. (mail coming - not sure about confidentiality)
- Action : "test - Open - Loop"
- Parameters : Repetition : 1000 , Averaging : 100
- CAMKE_BUILD_TYPE : SDK & CEP both Release
- exact output ( full console in joined text)
Average time for 100 firsts : 14.81 ms
Average time for 100 lasts : 207.01 ms
Average time for all : 87.516 ms
Total time : 87.516 s

ps: there is a little bug on console display during Application::open on the images (several blank lines)

RE: slow-down in the opening of many images [ reply ]
By: Emmanuel Promayon on 2016-03-12 11:53
[forum:3564]
Dear Aurelien,

Thank you for this post, it turns out to be very interesting!
It is a great idea to have provided a specific CEP sourcecode (reproducible test!).

It might be an I/O problem. I would like to try the same thing on Linux, just to check if it is OS or filesystem dependent.

To test the exact same thing, would you mind:
- to send me an mhd+raw (or mha) file sample that I can duplicate to try with your CEP? (send it using private email if it may convey any confidential information).
- to post all the following information :
- the name of the action you use (test loop or test dir) (I suppose test loop is easier to use with mhd)
- the values of your parameters (averaging/repetition)
- the values of CMAKE_BUILD_TYPE used to compile the SDK and your CEP
- the exact output of your action, something like:
Average time for xxx firsts : xxx ms
Average time for xxx lasts : xxx ms
Average time for all : xxx ms
Total time : xxx s

I will then try the exact same thing and if I have the same types of results, run the program with a profiler to check if this can be optimized.

Thanks in advance,
Mahnu

PS: to compile on linux I had to force the CXX_FLAGS to -std=c++11 and to change #include <time.h> to #include <ctime>


slow-down in the opening of many images [ reply ]
By: Aurélien Jaffard on 2016-03-09 18:53
[forum:3557]

testouverture.zip (19) downloads
Hello all,

I have to open quite a large number of images
and I experiencing an important slowdown.

for example, on opening 1000 images:
- the first 100 have an average opening time of 15 ms each
- the last 100 have an average opening time of 240 ms each

for example, on opening 2000 images:
- the first 100 have an average opening time of 15 ms each
- the last 100 have an average opening time of 1300 ms each

I don't understand from what it comes,
- It is not limited by RAM only 50% full (image are small : mhd + row 320kB each)
- It is no limited by CPU only 20% usage

Could you please help me to understand this.


Joined : my test CEP if you want to try


   
Powered By FusionForge