Sign in to vote. User posted Here is new feature of ASP. Thursday, November 10, AM. User posted ASP. Thursday, November 10, PM. User posted Of course is the Asp. Tuesday, November 15, PM. Wednesday, November 16, AM.
Where the biggest slowdowns in web applications happen tends to be remote services, especially database persistence. PHP is programmed without the benefit of connection pooling, or in-memory session state. This can be overcome with memcached and other, more performant service layers also available to. A similar site under PHP would likely fall under its own weight. Other things to consider. IIS vs.
Honestly the php vs asp. PHP doesnt lend itself well to large, complex applications nearly so much as asp. I'd tend to agree with you that ASP. For example, create a table with 1,, rows containing a sequential primary key, and then a random in the second column.
Each of your sites can accept the primary key in a GET, retrieve the random based on the passed in key, and display the random in some type of dynamically generated html. I'd love to know the results It would be even better if you could build this simple little app in regular ASP too. Heck, I'd even pay you for these results if the test was well designed. Seriously - just express your interest here and I'll send you my e-mail. Need to note that question is. I don't have the facts, but general feeling is PHP websites run faster than.
NET Web form sites and I do. NET only. NET web forms despite being compiled vs interpreted PHP is generally slow because all the chunk of code that is autogenerated by the. Getting a. Now, MVC is a different story, I had made two websites using. NET will win on performance in a windows server ecosystem. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow.
Learn more. Speed of code execution: ASP. Asked 12 years, 7 months ago. Active 3 years, 4 months ago. Viewed 67k times. Improve this question. So here is a fine example of an awesome project using ASP. Source please?. Add a comment. Active Oldest Votes. Ultimately though I think you're arguing what's really an irrelevant detail. Improve this answer. NET" - there is no interpretation for Java or. NET whatsoever. In the end only native code is executed. Excellent and insightful comparison.
But I have to point out one thing " NET to release code changes. Tion I'm less familiar with ASP. NET hot deploys than some other frameworks but in Java for example you can drop in JSP files and sometimes can reload classes but in a lot of cases you simply need to restart.
How does that compare? All comparison made in this reply seems to be PHP vs. NET web forms. About that I can say PHP is faster than. NET in real world and practical scenarios I still want to see some comparisin PHP vs. Update on. NET Core check this and this post, it says. Show 2 more comments. Buy fast computer, and enjoy it if you do serious business web applications ASP. Kamil Orzechowski Kamil Orzechowski 4 4 silver badges 2 2 bronze badges.
Sheesh, mentioning LINQ says everything. But, most of the time, we talk about the mostly hated LINQ to SQL, that is fine for small projects but it is useless for anything complex. And it is valid for. Check Entity Framework for instance. StackOverflow is a case in point, having used a lot of LINQ, but then having backed a lot of it out for performance reasons and replacing it with their own homegrown micro-ORM.
LINQ itself is generally fine to outstanding. It was the next super-obvious evolution once Microsoft got extension methods into C thank you Objective-C!!!! But similar with a lot of other language-choice related questions the following statement is in this case valid in my opinion : There are slow, buggy sites in language x be it PHP or Asp. Net What i'm trying to say: the talents of the developer will influence the overall speed more than a choice between two roughly equivalent in some abstracted extent technologies.
ChristopheD ChristopheD k 27 27 gold badges silver badges bronze badges. The difference is quite spectacular. The server can now make intelligent decisions about the page content and push resources down before they are even requested.
Compression is a great tool for reducing the amount of data sent over the wire, but all the compression algorithms used to send HTML, CSS and JavaScript are lossless compression algorithms. With some understanding of what it is that is being compressed, we can eek out some additional gains in size reduction. For instance, the JavaScript. This is because the scope of the variables is entirely private and the whitespace largely unnecessary.
This process is called minification. To understand the reasoning here, you need to understand a little bit about how browsers achieve their incredible speed. When downloading a page, the browser will attempt to start rendering the application as soon as it has any content.
When the browser realizes that it has made an incorrect guess about how the page should be rendered, then all the work that was done needs to be thrown out and started over again. One of the things which causes one of these reflows is the addition of a new stylesheet.
Load style sheets first to avoid having a style that alters an already-rendered element. JavaScript is a complete about-face from CSS, and should be loaded last. This is because we want the page to render as quickly as possible, and JavaScript is not typically necessary for the initial render. Users will typically take a moment to read the page and decide what to do next. You may wish to investigate loading only the JavaScript necessary to bootstrap the application, and loading more in the background.
If speed is really important, you can even investigate what are called isomorphic or universal applications.
The pages in these applications are rendered on the server side, and then the JavaScript application attaches to the already-rendered HTML and takes over from there. Thes applications have the advantage of being fast to load without giving up the seamless nature of single page applications.
In an ideal world, your site would contain no images at all. It is typically a lot more efficient to use inline-SVG or CSS tricks to create vector art for your pages because they are far smaller than raster images. Figuring out the right encoding settings can be difficult, but there are some really impressive services to do it for you. I quite like this tinypng service , and only just a little bit because it has a cool panda for a logo.
There are also plugins for your JavaScript build tool that perform much of the same optimization, but sadly without the panda. ORMs object-relational mappers have been highly beneficial in increasing developer productivity, however they provide a layer of abstraction that can introduce sub-optimal queries. It is surprising how easy it is to fix these problems by using eager loading over lazy loading, and examining projections.
Very frequently, the data on your pages changes at a slow pace. As an example, the hot questions page on Stack Overflow could be updated in real time, but the data changes are not significant enough to bother re-querying the database. Instead of taking a hit going to the database and re-rendering a complex looking page, we can shove the page into a cache and serve subsequent requests using that data. If you happen to be using ASP. NET MVC caching, the response from an action is as simple as adding a single attribute to the action.
Caching the entirety of a page may not be exactly what you want, in which case tip 12 is for you. You may want to cache only part of your page; this is colloquially known as donut hole caching.
It is a useful approach when you have user-specific data mixed with general data on the same page. The user data varies by the user, while the rest of the page is the same for all users. The sections highlighted in green are cached per page and orange are cached per user. There are a ton of content delivery networks, which have edge nodes very close to wherever your users might be.
0コメント