Gone are the days when 64-bit memory against the prerogative of Itanium, SPARC, RISC, PowerPC, etc. Now almost every desktop PC based on x86-64 architecture, let alone servers. 64 has become cheap, opening new horizons for a variety of applications.
Surely, those who run (or are about to run) x64 platformS to think long term bother to migrate to 64 today will pay off manifold in the long run.
Migration to 64 bits becomes a particularly sensitive issue when it comes to image processing. If you have not dealt with anything larger than 5000x5000 pixels, probably would not be reading this article. Otherwise, you might witness its launch applications 'memory' errors from time to time - and think about lifting the curse of 2 GB per process. Install more memory (if necessary) and switch to the x64 platform - is often as simple as that. This was essentially the main idea behind the mill bear x64here in Aurigma Graphics.
However, the nature (often apparently) cumbersome and costly 64-bit migration is often the key to say "no" to the natural solution to the problem. Therefore, developers are forced to find the roundabouts 'out of memory' anxieties. Some of these "remedies" are highly charged performance of tax and are consequences for development and debugging. They are often outweigh the potential benefits. Furthermore, the development added \ treatment costs often exceed the cost of migrating an entire farm of 64 bits.
On the other hand, more and more applications and services are transferred to 64 and some are native 64-bit - and no longer limited to scientific computing and complex tasks of mathematical modeling. In fact, for x64 servers has become an industry standard for a while. Therefore, if you have a 32-bit legacy applications that prevents the change of his permanent IIS 64-bit, I would reply with a standard marketing call to action: "Think big - go 64! ', O even more annoying - 'Extending your address space now ".
So, what are the costs of saying goodbye to "outside members? In Graphics Mill for. NET, which means replacing a couple of DLLs in the API. If you ask me, I would say it is not definitely worth trying at least. At the end, it's up to you to decide if the stay of 86 and reinvent the page file "or" harness the raw power of raw x64 "(I think I can the two for future use).