AnyCPU vs. x64
#1852
Replies: 1 comment
-
There will be a tiny performance improvement because you will skip an if statement that decides if the 32-bit or 64-bit path should be used. And there will be a reduction in download size during development. However if you exclusively target x64 I would recommend you to use the X64 version. But if you have people using this on an Arm64 machine I would advise you to stay with the AnyCPU version. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
For my first project I used the 'Magick.NET-Q16-AnyCPU' package, just because it was the topmost, which had the most downloads. I am however developing exclusively for 64 bit Windows and thus thinking about 'Q16 Magick.NET-Q16-x64' instead. The difference just seems to be that the DLL 'Magick.NET-Q16-AnyCPU.dll' is replaced by 'Magick.NET-Q16-x64.dll' (?), which makes little difference in regard to disk storage.
Is there any difference in performance?
I am about to migrate quite a few smaller solutions from VisualBasic Script to Magick.NET. Thus this decision will affect all of the exe-files created, which I am planning to place all in the same folder, together with the Magick.NET runtime DLLs.
Beta Was this translation helpful? Give feedback.
All reactions