When I create Azure Functions, it will set "Platform 32-bit" for default. However I normally set ASP.NET MVC, OWIN or any other projects as 64bit.
Platform 32-bit for default
I'm wondering with "What the difference with 32-bit or 64-bit for Azure Functions"?
I guess this effects with NuGet Package reference and Memory allocation. However as Azure Functions can only available to assign up to 1536 MB, therefore 32-bit or 64-bit would be no effects at all.
Is there any definite reason or recommendation to set 64-bit? Any advice will be very much appreciated.
Azure Functions are always static methodsActions of Web API, with the aid of using the way, don't have the static modifier. This outcome in a good-sized architectural extrude at some stage in the migration, specifically with dependency injection (DI).
Azure Functions provides writing functions in different programming languages, e.g., C#, Java, or python, and it supports Windows and Linux. There are endless scenarios für Azure functions, like running scheduled tasks, analyzing IoT data streams, or building a web (REST) API.
I would not suggest switching the Functions worker process to 64 bit. It will not run any better, and the memory usage will end up being higher (as it always is for 64 bit). Also, at this point Functions has only been tested in 32 bit mode so you may run into some unexpected issues in 64 bit.
Update (2/6/2017): see this question for latest, as well as https://github.com/projectkudu/AzureFunctionsPortal/issues/894.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With