Comments on: C# Image Processing Performance – Unsafe vs. Safe code, Part I

By: Bitmap-Binary Basics

Bitmap-Binary Basics — Mon, 01 Feb 2010 16:47:39 +0000

[...] To use ’safe’ code the actual program execution would take forever. So there may be a third alternative worth looking into. And here are more thoughts about this. This is something we are going to have [...]

By: Kim Jensen

Kim Jensen — Wed, 13 Aug 2008 14:24:26 +0000

Very nice and clean demonstration. And yes, getPixel/setPixel really does suck extremely bad :-)

By: david

david — Thu, 26 Jun 2008 20:47:33 +0000

I wasn’t aware of that possibility. Perhaps I’ll look into it and post a follow-up.

By: whatif

whatif — Thu, 26 Jun 2008 11:23:19 +0000

What if you used Buffer class to do the block copy for your bitmap data in the first example?

By: david

david — Wed, 02 Apr 2008 00:10:17 +0000

Yup, Part II has the results. The link to part II is right above your comment in the trackback.

By: olof

olof — Tue, 01 Apr 2008 22:49:23 +0000

so where did the performance comparison go..? Part two ? :) Really interested in what you found!

By: Obnoxiously Verbose / C# Image Processing Performance - Unsafe vs. Safe code, Part II

Fri, 14 Mar 2008 09:46:40 +0000

[...] out Part I of this [...]