new Aurigma.GraphicsMill.Bitmap() much slower on win2008

I'm having some performance issues using Aurigma.GraphicsMill.Bitmap. The following code runs 10 times slower on

Windows 2008 server compared to Windows 2003 server. Both servers are virtual machines, with the following specs:

The specs for the servers are:

Win 2008 32bit

CPU: 8 x Intel Xeon E5335 @2.00Ghz

RAM: 8 GB

Win 2003 32bit

CPU: single Intel Core 2 660 @2.40 Ghz

RAM: 766 MB

I am using version 5.1.276.0 of Graphics Mill

Here's the code for a simple console app that demonstrates the problem:

class Program
    {
        static void Main(string[] args)
        {
            int counter = 1;
            if (args.Length > 0)
            {
                int.TryParse(args[0], out counter);
            }

            Console.WriteLine("Creating and disposing of {0} Aurigma.GraphicsMill.Bitmap objects sequentially...",counter );
            
            //grab the test image from embedded resource
            System.Drawing.Bitmap testImage = Resource1.testimage; //~3.5M JPEG 

             counter = Math.Abs(counter);
            DateTime start = DateTime.Now;
            for (int i = 1; i <= counter; i++)
            {
                using (Aurigma.GraphicsMill.Bitmap hiResBmp = new Aurigma.GraphicsMill.Bitmap(testImage))
                {

                }

            }

            double ms = DateTime.Now.Subtract(start).TotalMilliseconds;
            Console.WriteLine("{0} Bitmaps took {1} ms", counter, ms);

        }
    }

To give you some example numbers, creating 10 Bitmaps takes 1 second on my Win2003 box, but takes 12 seconds on Win2008! I have tested on other Win2008 and Win2003 servers, with similar results.

I have profiled this code using Jetbrain's dotTrace profiler & looked at the Graphics Mill code using reflector. The call stack to the hot spot is this:

Aurigma.GraphicsMill.Bitmap..ctor(Bitmap)
    Aurigma.GraphicsMill.Bitmap._Create(Bitmap)
       Aurigma.GraphicsMill.Bitmap._Create(Int32, Int32, PixelFormat, ColorPalette, Color)
         ?Create@BitmapData@ImagingFramework@@$$FQAEXKKW4PixelFormat@2@PBVColorMap@2@@Z*

I have 2 questions:

(1) can anyone reproduce this? (if not, what the hell am i doing wrong! )

(2) if it's reproducable, is it something that can be fixed in a future release?

cheers,

Sherwin

p.s have attached the console app that demonstrates the problem. Execute it like this:

C:\>bitmaptest 10

Creating and disposing of 10 Aurigma.GraphicsMill.Bitmap objects sequentially...

10 Bitmaps took 1462.1024 ms

Edited by user Sunday, September 6, 2009 9:05:39 PM(UTC)  | Reason: Not specified

File Attachment(s):

BitmapTest.rar (3,555kb) downloaded 2 time(s).

Win2003.dtc (374kb) downloaded 2 time(s).

Win2008.dtc (562kb) downloaded 3 time(s).

testimage.jpg (3,477kb) downloaded 2 time(s).

I have attached the JPEG i am using for testing to my original post. I've also attached the trace files created by Jetbrains dotTrace, you can get a free evaluation copy from http://www.jetbrains.com/profiler/download/index.html if you dont already have it. As you can see, there is a massive difference in time spent within the call to:?Create@BitmapData@ImagingFramework@@$$FQAEXKKW4PixelFormat@2@PBVColorMap@2@@Z*

Unfortunately i have not been able to test this on a *real* server: all my tests have been done on virtual machines provided by my hosting company. Have you tried running my attached test app on a *virtual* Windows 2008 machine?

I'll have a go at removing the System.Drawing.Bitmap dependency as you suggested.

Cheers,

Sherwin

Sorry for the delay. Here are my results, each for 10 iterations run:

• Vista x64 (Core2 Duo 1.86Ghz): ~700 ms

• Windows Server 2008 on Virtual PC (Core2 Duo 1.86GHz): ~2500 ms

• Windows Server 2008 on Virtual Server (Dual Xeon 3GHz): ~2200 ms

As for profiling snapshots - they look strange. As I can see they were got from rather different code, so its hard to compare them. I can see that Bitmap ctor on Win2003 works much faster, but I'm not sure that it has same input params as in Win2008 code. Also there is maybe some cache/optimization specific.

Beside that, it seems that Win2008 virtual machine works 5 times slower than Win2003 box (at least, in snapshots data) - take a look at main module ..ctor and SingleDomainUnload() timings.

Please, could you provide profiling snapshots for the same code & input? And, it will be great, if this code works with Graphics Mill only, without System.Drawing objects in the middle.

I will be looking forward for you answer, sorry again for a such delay.

Best regards,

Alex Kon.