“平台32位"与“平台32位"之间有什么区别吗?或“平台64位"用于Azure功能? [英] Is there any difference between "Platform 32-bit" or "Platform 64-bit" for Azure Functions?

查看:100
本文介绍了“平台32位"与“平台32位"之间有什么区别吗?或“平台64位"用于Azure功能?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

当我创建Azure Functions时,它将默认设置"32位平台".但是,我通常将ASP.NET MVC,OWIN或任何其他项目设置为64位.

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.

默认为32位平台

我想知道"Azure功能与32位或64位有何区别"??

我想这与NuGet包参考和内存分配有关.但是,由于Azure功能只能分配多达1536 MB的空间,因此32位或64位完全没有效果.

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.

是否有确定的理由或建议设置64位? 任何建议将不胜感激.

Is there any definite reason or recommendation to set 64-bit? Any advice will be very much appreciated.

推荐答案

我不建议将Functions辅助进程切换为64位.它不会运行得更好,并且内存使用率最终会更高(因为它始终是64位).另外,此时功能仅在32位模式下进行了测试,因此您可能会在64位模式下遇到一些意外问题.

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.

更新(2/6/2017):请参见 https://github.com/projectkudu/AzureFunctionsPortal/issues/894 .

Update (2/6/2017): see this question for latest, as well as https://github.com/projectkudu/AzureFunctionsPortal/issues/894.

这篇关于“平台32位"与“平台32位"之间有什么区别吗?或“平台64位"用于Azure功能?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆