[Insight-users] Performance regression in ITK + gdcm 2.0 reading DICOM JPEG files

[Roger Bramon Feixas]

Hi Brad,

Sorry, I didn't mention it but in this performance test I used ITK 3.16
patched in order to solve the bug related to the UpdateOutputInformation.
The patch was applied based on your commit. The other versions are stock
versions.

Roger



On Fri, May 14, 2010 at 1:05 PM, Bradley Lowekamp <blowekamp at mail.nih.gov>wrote:

> Hello Roger,
>
> That looks like a nice table to look at for performance analysis!
>
> Are your versions of ITK stock? I am surprised at the results because of
> the bug that we fix related to the UpdateOutputInformation taking too long.
> I expected that to be costly in 3.16, but better in 3.18.
>
> Brad
>
> On May 13, 2010, at 5:00 PM, Roger Bramon Feixas wrote:
>
> > Hi,
> >
> > Recently we updated our ITK version from ITK 3.16 to ITK 3.18 and we
> decided to relink ITK with system GDCM 2.0. After some tests, we concluded
> ITK 3.18+GDCM 2.0 is faster than ITK 3.18 reading DICOM Little Endian files,
> however ITK 3.18+GDCM 2.0 is rather slower reading DICOM JPEG files. I
> attach a PDF file which is a time comparison of ITK 2.8, 3.16, 3.18 and
> 3.18+GDCM2.0 versions.
> >
> > I don't know if it's just a GDCM problem or if it depends on how ITK uses
> GDCM.
> >
> > Thanks for your attention,
> >
> > Roger
> > <Performance ITK + gdcm 2.pdf><ATT00001..txt>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/pipermail/insight-users/attachments/20100514/fbfb9d75/attachment-0001.htm>