ASP.NET MVC VS WebForms的第一页的大项目载入速度 [英] ASP.NET MVC vs WebForms for First Page Load Speed for Big Projects

查看:132
本文介绍了ASP.NET MVC VS WebForms的第一页的大项目载入速度的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们有很多其他库的引用的pretty大ASP.NET Web窗体(Web应用程序)的项目外,其他项目等,大部分的编译后的时候,我们第一次加载它需要一个页面任何渲染了很久才...磁盘IO是主要问题。对于小项目,它几乎是即时的,但一旦你的项目变大,才能够真正发展缓慢,并从节目中删除的乐趣。

We have a pretty big ASP.NET WebForm (web application) project with a lot of references to other libraries, other projects etc and most of the time after a compilation, the first time we load a page it takes a LONG time before rendering anything... Disk IO is the main problem. For small projects it's nearly instantaneous, but once your project gets large, it can really slow development and remove fun from programming.

我的问题:
首先页面加载时间,只要在ASP.NET MVC,因为它是在ASP.NET Web表单的大项目?编译后

My question: Is first page load time after a compilation as long in ASP.NET MVC as it is in ASP.NET Webforms for big projects?

推荐答案

MVC仍然使用相同的ASP.NET框架Web窗体,所以你可能会看到类似的行为,不管。

MVC still uses the same ASP.NET framework as Web Forms, so you are probably going to see similar behavior, regardless.

长条的第一加载时间是因为你的项目的构建输出仍然只是IL code,需要由JIT编译器执行之前编译到code。你做将导致previously缓存本地code为您的应用程序的任何code的改变被丢弃,所以JIT有重新编译。当然,更大的项目,时间越长,要采取的JIT处理它。

The long first load time is because your project's build output is still just IL code that needs to be compiled into native code by the JIT compiler before executing. Any code changes that you make will cause the previously cached native code for your app to be discarded, so the JIT has to recompile. Naturally, the larger your project, the longer it's going to take for the JIT to process it.

这篇关于ASP.NET MVC VS WebForms的第一页的大项目载入速度的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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