We've started porting our video processing pipeline from Windows to Linux and we're seeing that many of the Linux IPP routines are slower than the Windows version. In particular the resizers such asippiResizeFilter_8u_C1R() using theippResizeFilterLanczosfilter option.
General question: is it expected that the Linux IPP routines perform the same as the Windows equivalets?
Note that I've performed the timing test on two identical HW platforms which have dual Xeon X5680 3.33GHz CPUs.
Chuck De Sylva (Intel) wrote:That's how I tend to time IPP routines. I put a timer just around the call, run it in a long loop, and then get a moving average. One thing I've noticed (at least under Windows), is that if you have a lot of other things happening in between the IPP call, you can get some IPP slowdown. It's like the call needs to be warmed up and then kept active. I would guess this has to do with cache misses, but I've even seen this where the image content changes from call to call. Peter
Another thing you can do is wrap timer calls around just the IPP code to narrow it down in both the Linux and Windows cases.
Sergey Kostrov wrote:I really liked OS/2 (even back to version 1.3). While everyone else at work was using Windows for Workgroups or Solaris, I used OS/2 since I could use Windows apps and Hummmingbird to access the Spac stations. At the time there was a goos book about the inner workings of OS/2 which I forget the name of.
>>...Windows vs. Linux...
By the way, in the middle of 1990th everybody was comparing Windows vs. OS/2 Wrap. Does anybody remember it? Unfortunately, OS/2 Wrap has not survived.
PS: Some time in June 1995, two months before a release of Windows 95, I had a very exciting dialog about Windows and OS/2 OSs with a very experienced system software developer and I will reproduce our conversation later...