PHP and ASP.NET go HEAD to HEAD

[showme]

PHP and ASP.NET Go Head-to-Head
By Sean Hull
http://otn.oracle.com/pub/articles/hull_asp.html


SUMMARY at the BOTTOM
Speed and efficiency. As I mentioned earlier, ASP.NET is a framework
allowing you to use various programming languages. In addition, it is touted
as having a great object-oriented model. All this is true, but it becomes a
detriment as far as speed is concerned. For all that advantage, there is a
lot more code to run through to execute the same ASP page than you have to
execute in the PHP engine for an equivalent PHP page. PHP is the
quick-and-dirty type of solution, the one to get the job done. And though a
lot of robustness has been added to it since its 2.0 and 3.0 days, it still
retains that core optimized high-speed approach.
Speed is not the only consideration. Memory usage is also important.



SECURITY COMPARISON
ASP.NET officially requires that you use IIS. Unfortunately, IIS has a long
history of vulnerabilities, which makes many administrators reluctant to
deploy it to handle their web site. Whether these weaknesses are because of
Microsoft's ineptness or because IIS is a real red flag to hackers is
irrelevant: Those systems have a history of being hacked and compromised.
PHP runs on Apache, too, which is fast and open source and has a good
security track record. Also, as I mentioned, Apache runs on many platforms.


So is PHP really faster than ASP.NET or is that for certain unoptimized
pages? And are they comparing this against the DataGrid instead of the
repeater control or even the fastest way using asp.net's inline code render
block, <% %>

comments?

[Simon Harvey]

Its a fair point, but to be fair the OO aspect is aimed at helping speed
development rather than speed execution. Most sites don't need blistering
speed and processors are getting faster and faster.

The speed issue is becoming less and less of an issue for the majority of
sites. I say this as a web host for many large sites including international
airports

Only one of our sites requires a dual 2.4 xeon machine

Our database server is also dual xeon.

Oh, and php is ugly imho

Let the flames begin

:-)

[Patrice]

The sad truth is that at some point you have to look at things against your
own requirements to make your own mind as you would do for choosing a car
(including both rational and unrelational arguments). That's life.

Patrice
--

Post by showme
PHP and ASP.NET Go Head-to-Head
By Sean Hull
http://otn.oracle.com/pub/articles/hull_asp.html
SUMMARY at the BOTTOM
Speed and efficiency. As I mentioned earlier, ASP.NET is a framework
allowing you to use various programming languages. In addition, it is touted
as having a great object-oriented model. All this is true, but it becomes a
detriment as far as speed is concerned. For all that advantage, there is a
lot more code to run through to execute the same ASP page than you have to
execute in the PHP engine for an equivalent PHP page. PHP is the
quick-and-dirty type of solution, the one to get the job done. And though a
lot of robustness has been added to it since its 2.0 and 3.0 days, it still
retains that core optimized high-speed approach.
Speed is not the only consideration. Memory usage is also important.
SECURITY COMPARISON
ASP.NET officially requires that you use IIS. Unfortunately, IIS has a long
history of vulnerabilities, which makes many administrators reluctant to
deploy it to handle their web site. Whether these weaknesses are because of
Microsoft's ineptness or because IIS is a real red flag to hackers is
irrelevant: Those systems have a history of being hacked and compromised.
PHP runs on Apache, too, which is fast and open source and has a good
security track record. Also, as I mentioned, Apache runs on many platforms.
So is PHP really faster than ASP.NET or is that for certain unoptimized
pages? And are they comparing this against the DataGrid instead of the
repeater control or even the fastest way using asp.net's inline code render
block, <% %>
comments?

[Cowboy (Gregory A. Beamer) [MVP]]

It is not a fair comparison (Oracle comparison), but I am sure there are
areas where PHP is faster. Even classic ASP beats ASP .NET in some areas.

Much of the benefit of .NET is not in the performance alone. Maintenance,
which is more expensive than perf in most cases, is greatly improved over
ASP and SO much easier than PHP.

But, everyone loves perf numbers. SO much so that I have seen sites that
were virtually unmaintanable, just to squeek out a few more cycles ... on a
site already running well below the bar. I call that STUPID, although some
may disagree! ;->
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************
Think Outside the Box!
************************************************

Post by showme
PHP and ASP.NET Go Head-to-Head
By Sean Hull
http://otn.oracle.com/pub/articles/hull_asp.html
SUMMARY at the BOTTOM
Speed and efficiency. As I mentioned earlier, ASP.NET is a framework
allowing you to use various programming languages. In addition, it is touted
as having a great object-oriented model. All this is true, but it becomes a
detriment as far as speed is concerned. For all that advantage, there is a
lot more code to run through to execute the same ASP page than you have to
execute in the PHP engine for an equivalent PHP page. PHP is the
quick-and-dirty type of solution, the one to get the job done. And though a
lot of robustness has been added to it since its 2.0 and 3.0 days, it still
retains that core optimized high-speed approach.
Speed is not the only consideration. Memory usage is also important.
SECURITY COMPARISON
ASP.NET officially requires that you use IIS. Unfortunately, IIS has a long
history of vulnerabilities, which makes many administrators reluctant to
deploy it to handle their web site. Whether these weaknesses are because of
Microsoft's ineptness or because IIS is a real red flag to hackers is
irrelevant: Those systems have a history of being hacked and compromised.
PHP runs on Apache, too, which is fast and open source and has a good
security track record. Also, as I mentioned, Apache runs on many platforms.
So is PHP really faster than ASP.NET or is that for certain unoptimized
pages? And are they comparing this against the DataGrid instead of the
repeater control or even the fastest way using asp.net's inline code render
block, <% %>
comments?

[Jerry Pisk]

I'm just going to add one more - MySQL is a lot faster than Oracle. Because
it doesn't support transactions and so on. Does it mean it's better? That
depends, the same way PHP versus Asp.Net depends. You're trading off
features for speed and most of the time it's those features that are going
to make your life a lot easier.

Jerry

Post by showme
PHP and ASP.NET Go Head-to-Head
By Sean Hull
http://otn.oracle.com/pub/articles/hull_asp.html
SUMMARY at the BOTTOM
Speed and efficiency. As I mentioned earlier, ASP.NET is a framework
allowing you to use various programming languages. In addition, it is touted
as having a great object-oriented model. All this is true, but it becomes a
detriment as far as speed is concerned. For all that advantage, there is a
lot more code to run through to execute the same ASP page than you have to
execute in the PHP engine for an equivalent PHP page. PHP is the
quick-and-dirty type of solution, the one to get the job done. And though a
lot of robustness has been added to it since its 2.0 and 3.0 days, it still
retains that core optimized high-speed approach.
Speed is not the only consideration. Memory usage is also important.
SECURITY COMPARISON
ASP.NET officially requires that you use IIS. Unfortunately, IIS has a long
history of vulnerabilities, which makes many administrators reluctant to
deploy it to handle their web site. Whether these weaknesses are because of
Microsoft's ineptness or because IIS is a real red flag to hackers is
irrelevant: Those systems have a history of being hacked and compromised.
PHP runs on Apache, too, which is fast and open source and has a good
security track record. Also, as I mentioned, Apache runs on many platforms.
So is PHP really faster than ASP.NET or is that for certain unoptimized
pages? And are they comparing this against the DataGrid instead of the
repeater control or even the fastest way using asp.net's inline code render
block, <% %>
comments?

[John Timney (Microsoft MVP)]

I've recently had to switch from a PHP app because its performance is not
good enough, however - theres not a web language on the planet that could
have performed to the standards we wanted, so its not a criticism on PHP.
ASP.NET could not have handled the job either and we were using mySQL rather
than Oracle.

What does this imply, well only that you have to take these things with a
pinch of salt, Oracle have an interest in saying this stuff on their site -
and the writer has an interest in more perople switching to PHP as it might
mean more work for him. So the view will typically be biased.

The conclusion should have actually demonstrated some real world
comparisons, including design issues, maintenence, server architectures,
speed of development etc. I think PHP 5 will have a lot to offer and will
only complment the available languages on the web - but head to head with
asp.net will need to be a few pages longer and a bit more fact driven than
what this chap has offered.

--
Regards

John Timney
Microsoft Regional Director
Microsoft MVP

Post by showme
PHP and ASP.NET Go Head-to-Head
By Sean Hull
http://otn.oracle.com/pub/articles/hull_asp.html
SUMMARY at the BOTTOM
Speed and efficiency. As I mentioned earlier, ASP.NET is a framework
allowing you to use various programming languages. In addition, it is touted
as having a great object-oriented model. All this is true, but it becomes a
detriment as far as speed is concerned. For all that advantage, there is a
lot more code to run through to execute the same ASP page than you have to
execute in the PHP engine for an equivalent PHP page. PHP is the
quick-and-dirty type of solution, the one to get the job done. And though a
lot of robustness has been added to it since its 2.0 and 3.0 days, it still
retains that core optimized high-speed approach.
Speed is not the only consideration. Memory usage is also important.
SECURITY COMPARISON
ASP.NET officially requires that you use IIS. Unfortunately, IIS has a long
history of vulnerabilities, which makes many administrators reluctant to
deploy it to handle their web site. Whether these weaknesses are because of
Microsoft's ineptness or because IIS is a real red flag to hackers is
irrelevant: Those systems have a history of being hacked and compromised.
PHP runs on Apache, too, which is fast and open source and has a good
security track record. Also, as I mentioned, Apache runs on many platforms.
So is PHP really faster than ASP.NET or is that for certain unoptimized
pages? And are they comparing this against the DataGrid instead of the
repeater control or even the fastest way using asp.net's inline code render
block, <% %>
comments?