Rick Brewster Posted December 6, 2005 Share Posted December 6, 2005 New, Jan. 19th 2006: I've made a video that clearly shows how much faster 64-bit is for Gaussian Blur. http://www.eecs.wsu.edu/paint.net/misc/ ... vs_x64.zip (fyi, it's a WMV) Just thought I'd give a preview of what to expect from Paint.NET v2.6 in the performance department. The good This benchmark was performed on an Athlon 64 2800+ underclocked to 900mhz (default clock is 1.8ghz) running Windows Server 2003 x64 Edition. It's underclocked because it's my personal server and I want it to use less power and run cooler (it's undervolted as well); it's generally disk bound, not compute bound, so the half clock speed doesn't affect what it does much. It does have 2 GB of RAM, but only because I had some spare DIMMs that wouldn't work in my other system. I opened a 1600x1200 image and performed a 100-pixel radius Gaussian blur. To do this correctly: 1. Open the image 2. Effects -> Blurs -> Gaussian Blur 3. Type 100 4. Hit OK 5. Press Cancel immediately 6. Press Ctrl+F 5 and 6 are necessary because we retain the 'preview' that was rendered so that it isn't recomputed when the user hits OK. It can save a lot of time when compared to v2.1. By adding these extra steps it makes sure that the entire effect rendering is benchmarked. The stop-watch timer started at step 6 and stopped when the progress dialog disappeared. Paint.NET v2.5, 32-bit on .NET 1.1 -- 3 minutes 14 seconds Paint.NET v2.6, 32-bit on .NET 2.0 -- 2 minutes 30 seconds Paint.NET v2.6, 64-bit on .NET 2.0 -- 1 minute 2 seconds Very nice. Not only has 32-bit performance improved for an operation that uses a lot of 64-bit math, but the x64 results are fantastic. 3x the performance is great! The bad Startup takes longer, with about 4-5x the number of pagefaults. (Edit: The number for page faults should only be 1.5-2x here, actually. I did not have the ngen.exe compilation set up correctly, so these results were for just-in-time compilation) Memory usage is about 20,000 K higher. I'm looking into this, but it may not be fixable right now. I am told that the 64-bit .NET Framework 2.0 is currently optimized for server workloads and that the client optimization will come in a future release or service pack. Probably won't be a big deal since most 64-bit systems are more modern with higher clock speeds and more memory than their average 32-bit counterparts. Oh, and startup is only slower for the 64-bit version. 32-bit startup is about the same. Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.