.NETGURU
  Search:  
NamespacesDiscussions.NET v1.1Dot Net Guru's BlogIT Certification
performance - ASP vs ASP.NET
Messages   Related Types
This message was discovered on ASPFriends.com 'aspngspeed' list.


hassan.hussein@zurich.com
-- Moved from [aspngfreeforall] to [aspngspeed] by Victor Von Doom <Click here to reveal e-mail address> --

Hi

A friend of mine who is into ASP argues that ASP is much faster than
ASP.NET.. that is render/display/data access. He says this whole dataset
thing is bound to be heavy and performance killer. he doesn't know much
about ASP.NET I only know a little more than him but believe in ASP.NET as
it wouldn't have come this far had it been much slower than ASP. I know
about the improvement in Code readability (separate HTML from Code), Server
controls, flexibility of ADO.NET, language neutrality and all that but what
i am interested now is just speed and would like to hear your input.

Thanks
Hassan
Reply to this message...
 
    
ToddC@match.com
DataSets are not the only method to get data into ASP.NET, as a matter of
fact for most web work you will be using DataReaders. DataReaders are
basically the same as fire hose recordsets. Very fast. Also, the SQLClient
and OracleClient namespaces were written using native communication
protocols, and are much faster than the OleDb counterparts.

Compiled code is awesome, and the benefits of such should not be
understated. ASP.OLD is interpreted for each request.

True OO development, when properly managed and exercised, will speed
development while also speeding up rework.

OutPutCaching is truly awesome, with no equivalent in ASP.Old.

View some stats at:
http://www.gotdotnet.com/team/compare/default.aspx

This is not a comparison of ASP.OLD with ASP.NET, but it does show that it
vastly out performs J2EE (10X faster!)

You only have to create a couple of pages to see the difference.

tc

-----Original Message-----
From: Click here to reveal e-mail address [mailto:Click here to reveal e-mail address]
Sent: Monday, August 19, 2002 9:43 AM
To: aspngspeed
Subject: [aspngspeed] performance -- ASP vs ASP.NET

-- Moved from [aspngfreeforall] to [aspngspeed] by Victor Von Doom
<Click here to reveal e-mail address> --

Hi

A friend of mine who is into ASP argues that ASP is much faster than
ASP.NET.. that is render/display/data access. He says this whole dataset
thing is bound to be heavy and performance killer. he doesn't know much
about ASP.NET I only know a little more than him but believe in ASP.NET as
it wouldn't have come this far had it been much slower than ASP. I know
about the improvement in Code readability (separate HTML from Code), Server
controls, flexibility of ADO.NET, language neutrality and all that but what
i am interested now is just speed and would like to hear your input.

Thanks
Hassan
| [aspngspeed] member Click here to reveal e-mail address = YOUR ID
| http://www.asplists.com/asplists/aspngspeed.asp = JOIN/QUIT
| http://www.asplists.com/search = SEARCH Archives
Reply to this message...
 
    
Joao Cardoso
One of the things you must take in consideration is that ASP.NET in debug
mode is quite slower than Release.
Also, you need to know that when you are coding, everytime you run your
project, asp.new will compile your application to a .dll file, and this
takes time of course.

If you run a release asp.net application, with codebehind, after the first
time, necessary to built the dll file, your asp.net app, if well built,
should be faster than the asp equivalent app. This is because asp is
interpreted (scripted), and asp.net is compiled. Also, memory manegment, and
connection pooling for sql server may improve quite a lot your perfomance.

Of course that all this depends on the way you code in asp.net, and asp. If
for instance you build your asp site, based on Visual C++ DLL files, perhaps
this is not quite true. But this depends a lot of what your are currently
using in asp and the way you code in asp.net.

Please mind that this is just a personal feedback, based on some
experience...

Best regards

Joao Cardoso

----- Original Message -----
From: <Click here to reveal e-mail address>
To: "aspngspeed" <Click here to reveal e-mail address>
Sent: Monday, August 19, 2002 3:43 PM
Subject: [aspngspeed] performance -- ASP vs ASP.NET

> -- Moved from [aspngfreeforall] to [aspngspeed] by Victor Von Doom
<Click here to reveal e-mail address> --
[Original message clipped]
Reply to this message...
 
    
Thomas Nielsen

I'm not the ultimate expert on ASP.NET performance, but I see a couple
of clear reasons why ASP.NET should be faster.

One is your code-behind is compiled to byte-code on first run. Granted,
its not compiled directly to the CPU, but to an intermediate language.
But executing this is still waaaaaay faster than any script-interpreter.

ASP.NET also incorporates some new caching mechanisms, which makes it
much easier for you to avoid re-generating data you already generated
once.

As a side note; ASP.NET makes the whole development process much faster,
so there's more money to buy hardware, if you look at it that way.
And since hardware keeps getting cheaper and cheaper, ASP.NET is
certainly "fast enough" for anything.

Regards,

Thomas Nielsen
AM Production Multimedia
=20

-----Original Message-----
From: Click here to reveal e-mail address [mailto:Click here to reveal e-mail address]=20
Sent: 19. august 2002 16:43
To: aspngspeed
Subject: [aspngspeed] performance -- ASP vs ASP.NET

-- Moved from [aspngfreeforall] to [aspngspeed] by Victor Von Doom
<Click here to reveal e-mail address> --

Hi

A friend of mine who is into ASP argues that ASP is much faster than
ASP.NET.. that is render/display/data access. He says this whole
dataset
thing is bound to be heavy and performance killer. he doesn't know much
about ASP.NET I only know a little more than him but believe in ASP.NET
as
it wouldn't have come this far had it been much slower than ASP. I know
about the improvement in Code readability (separate HTML from Code),
Server
controls, flexibility of ADO.NET, language neutrality and all that but
what
i am interested now is just speed and would like to hear your input.

Thanks
Hassan
| [aspngspeed] member Click here to reveal e-mail address =3D YOUR ID
| http://www.asplists.com/asplists/aspngspeed.asp =3D JOIN/QUIT
| http://www.asplists.com/search =3D SEARCH Archives
Reply to this message...
 
    
Alicianiah Cherry
My experience with ASP.NET vs. ASP is that ASP.NET is not really faster
that ASP, nor is it slower. I am using ASP.NET in a database intensive
application with a maximum of 120 simultaneous users, so the load on my
application is probably not heavy enough to make a difference. In any case,
I have not noticed a signficant increase or decrease performance wise
between the ASP and the ASP.NET implementation of the application. Someone
with experience in a larger user base may have different results, however.

Alicia

-----Original Message-----
From:    Click here to reveal e-mail address [SMTP:Click here to reveal e-mail address]
Sent:    Monday, August 19, 2002 10:43 AM
To:    aspngspeed
Subject:    [aspngspeed] performance -- ASP vs ASP.NET

-- Moved from [aspngfreeforall] to [aspngspeed] by Victor Von Doom
<Click here to reveal e-mail address> --

Hi

A friend of mine who is into ASP argues that ASP is much faster than
ASP.NET.. that is render/display/data access. He says this whole dataset
thing is bound to be heavy and performance killer. he doesn't know much
about ASP.NET I only know a little more than him but believe in ASP.NET as
it wouldn't have come this far had it been much slower than ASP. I know
about the improvement in Code readability (separate HTML from Code), Server
controls, flexibility of ADO.NET, language neutrality and all that but what
i am interested now is just speed and would like to hear your input.

Thanks
Hassan
| [aspngspeed] member Click here to reveal e-mail address = YOUR ID
| http://www.asplists.com/asplists/aspngspeed.asp = JOIN/QUIT
| http://www.asplists.com/search = SEARCH Archives
Reply to this message...
 
    
Alex Lowe
Hassan,

The bottom line is there are many feature/technical reasons why ASP.NET
*should* be faster/better than classic ASP
(http://www.aspng.com/freebook/learn/overview.aspx is a decent list).

Everyone on this list can tell you that ASP.NET is faster but what will
that do? Will it make you a believer? Will it make your colleague a
believer? I doubt it. You will not believe it until you setup your
benchmarks that you can reproduce and point people too (or you build
some successful applications). I suggest (as someone else did) you check
out the PetShop sample application
(http://www.gotdotnet.com/team/compare/). I don't suggest you check it
out because it will convince you of anything but I suggest you check it
out because I think it will give you an idea of how one should go about
setting up a performance test (tools to use, etc.).

Happy benchmarking!

Alex - AspFriends.com Moderation Team
Microsoft MVP - ASP.NET

***********************************************************
Translate C# code to VB.NET code at
http://aspalliance.com/aldotnet/examples/translate.aspx
***********************************************************

[Original message clipped]
Reply to this message...
 
    
hassan.hussein@zurich.com

Thanks Todd for the input.

I must have undermined my knowledge. I know about DataReaders (Read only
access to DB) and that SQLClient is faster than the more generic
OLEDBProvider. Compiled code should be faster but that is not the only
thing I expected ASP.NET. I expected a large number of fine tunings to
perform better.

What is the OutPutCaching? Are there optimisations for speed.

What is the percieved result performance-wise of running two tiny apps (say
read all Employees from Northwind dB and display them in a grid in both
ASP.OLD and ASP.NET. I would be surprised if nobody has ever tried any
benchmarks. If not me and my friend will have to do the benchmarks.
Having said that I would like to be armed with all possible ways of
optimising an ASP.NET app so that justice is done as my friend has done
quite a lot of ASP development, whereas I haven't done anything with
ASP.NET ohter than read a DB and display.

Cheers
Hassan

ToddC@match.c
om To: "aspngspeed" <Click here to reveal e-mail address>
cc:
19/08/2002 Subject: [aspngspeed] RE: performance -- ASP vs ASP.NET
04:41 PM
Please
respond to
"aspngspeed"

DataSets are not the only method to get data into ASP.NET, as a matter of
fact for most web work you will be using DataReaders. DataReaders are
basically the same as fire hose recordsets. Very fast. Also, the
SQLClient and OracleClient namespaces were written using native
communication protocols, and are much faster than the OleDb counterparts.

Compiled code is awesome, and the benefits of such should not be
understated. ASP.OLD is interpreted for each request.

True OO development, when properly managed and exercised, will speed
development while also speeding up rework.

OutPutCaching is truly awesome, with no equivalent in ASP.Old.

View some stats at:
http://www.gotdotnet.com/team/compare/default.aspx

This is not a comparison of ASP.OLD with ASP.NET, but it does show that it
vastly out performs J2EE (10X faster!)

You only have to create a couple of pages to see the difference.

tc

-----Original Message-----
From: Click here to reveal e-mail address [mailto:Click here to reveal e-mail address]
Sent: Monday, August 19, 2002 9:43 AM
To: aspngspeed
Subject: [aspngspeed] performance -- ASP vs ASP.NET

-- Moved from [aspngfreeforall] to [aspngspeed] by Victor Von Doom
<Click here to reveal e-mail address> --

Hi

A friend of mine who is into ASP argues that ASP is much faster than
ASP.NET.. that is render/display/data access. He says this whole dataset
thing is bound to be heavy and performance killer. he doesn't know much
about ASP.NET I only know a little more than him but believe in ASP.NET as

it wouldn't have come this far had it been much slower than ASP. I know
about the improvement in Code readability (separate HTML from Code), Server

controls, flexibility of ADO.NET, language neutrality and all that but what

i am interested now is just speed and would like to hear your input.

Thanks
Hassan
| [aspngspeed] member Click here to reveal e-mail address = YOUR ID
| http://www.asplists.com/asplists/aspngspeed.asp = JOIN/QUIT
| http://www.asplists.com/search = SEARCH Archives

| [aspngspeed] member Click here to reveal e-mail address = YOUR ID
| http://www.asplists.com/asplists/aspngspeed.asp = JOIN/QUIT
| http://www.asplists.com/search = SEARCH Archives
Reply to this message...
 
    
Fabio Yeon
Performance questions, especially those of X vs. Y, are sometimes
difficult to answer, mostly because performance is not only technology
related, but also implementation and application requirements related.

Having said that, here's some data to help you out.

A typical DB app that reads rows of data and renders on the screen will
typically be faster on ASP.NET than ASP. The combination of ADO.NET
(especially with the fast and light SQLDataReader), compiled code and
optimizations in the request pipeline gives a pretty good jump for
ASP.NET. I've measured performance improvements from 2x to over 5x on
some simple pages (same tests run on same hardware).

Output caching is also a great performance booster, if used well. It
simply means that the output of a page can be cached (based upon user
set configuration) so that subsequent requests to it don't even run the
page code to return the response. Imagine scenarios like inventory
pages that are output cached for 5 minutes at a time. The server would
be able to support very high throughput levels, while the page code is
hit once every 5 minutes or so to obtain a refresh. Of course, this
assumes that it's ok to have the data on the web page updated only every
5 minutes... But you can imagine the possibility for things like store
catalogs, etc.

Also, there are good stories of ASP.NET migration from customers and
other folks in various forums. The site www.gotdotnet.com may be of
help here.

Finally, if and when you're ready to dive into some performance fine
tunings for your apps, there is a short white paper that should help you
out. It's available at:
http://www.gotdotnet.com/team/asp/ASP.NET%20Performance%20Tips%20and%20T
ricks.aspx

Hope this helps.

-----Original Message-----
From: Click here to reveal e-mail address [mailto:Click here to reveal e-mail address]=20
Sent: Monday, August 19, 2002 8:59 AM
To: aspngspeed
Subject: [aspngspeed] RE: performance -- ASP vs ASP.NET

Thanks Todd for the input.

I must have undermined my knowledge. I know about DataReaders (Read
only access to DB) and that SQLClient is faster than the more generic
OLEDBProvider. Compiled code should be faster but that is not the only
thing I expected ASP.NET. I expected a large number of fine tunings to
perform better.

What is the OutPutCaching? Are there optimisations for speed.

What is the percieved result performance-wise of running two tiny apps
(say read all Employees from Northwind dB and display them in a grid in
both ASP.OLD and ASP.NET. I would be surprised if nobody has ever tried
any benchmarks. If not me and my friend will have to do the benchmarks.
Having said that I would like to be armed with all possible ways of
optimising an ASP.NET app so that justice is done as my friend has done
quite a lot of ASP development, whereas I haven't done anything with
ASP.NET ohter than read a DB and display.

Cheers
Hassan

=20

ToddC@match.c

om To: "aspngspeed"
<Click here to reveal e-mail address> =20
cc:

19/08/2002 Subject: [aspngspeed] RE:
performance -- ASP vs ASP.NET =20
04:41 PM

Please

respond to

"aspngspeed"

=20

=20

DataSets are not the only method to get data into ASP.NET, as a matter
of fact for most web work you will be using DataReaders. DataReaders
are basically the same as fire hose recordsets. Very fast. Also, the
SQLClient and OracleClient namespaces were written using native
communication protocols, and are much faster than the OleDb
counterparts.

Compiled code is awesome, and the benefits of such should not be
understated. ASP.OLD is interpreted for each request.

True OO development, when properly managed and exercised, will speed
development while also speeding up rework.

OutPutCaching is truly awesome, with no equivalent in ASP.Old.

View some stats at: http://www.gotdotnet.com/team/compare/default.aspx

This is not a comparison of ASP.OLD with ASP.NET, but it does show that
it vastly out performs J2EE (10X faster!)

You only have to create a couple of pages to see the difference.

tc

-----Original Message-----
From: Click here to reveal e-mail address [mailto:Click here to reveal e-mail address]
Sent: Monday, August 19, 2002 9:43 AM
To: aspngspeed
Subject: [aspngspeed] performance -- ASP vs ASP.NET

-- Moved from [aspngfreeforall] to [aspngspeed] by Victor Von Doom
<Click here to reveal e-mail address> --

Hi

A friend of mine who is into ASP argues that ASP is much faster than
ASP.NET.. that is render/display/data access. He says this whole
dataset thing is bound to be heavy and performance killer. he doesn't
know much about ASP.NET I only know a little more than him but believe
in ASP.NET as

it wouldn't have come this far had it been much slower than ASP. I know
about the improvement in Code readability (separate HTML from Code),
Server

controls, flexibility of ADO.NET, language neutrality and all that but
what

i am interested now is just speed and would like to hear your input.

Thanks
Hassan
| [aspngspeed] member Click here to reveal e-mail address =3D YOUR ID=20
| http://www.asplists.com/asplists/aspngspeed.asp =3D JOIN/QUIT=20
| http://www.asplists.com/search =3D SEARCH Archives

| [aspngspeed] member Click here to reveal e-mail address =3D YOUR ID=20
| http://www.asplists.com/asplists/aspngspeed.asp =3D JOIN/QUIT=20
| http://www.asplists.com/search =3D SEARCH Archives

| [aspngspeed] member Click here to reveal e-mail address =3D YOUR ID=20
| http://www.asplists.com/asplists/aspngspeed.asp =3D JOIN/QUIT=20
| http://www.asplists.com/search =3D SEARCH Archives
Reply to this message...
 
 




ExamGuru IT Solutions - .Net Guru is owned and operated by ExamGuru, Inc., the man behind .Net Guru. If you're in the market for bespoke software or software consultancy, why not get him and his highly trained team to help? - www.examguru.net/ITCertification
Ad


Need Dot Net Interview Questions?
Ask ExamGuru, Inc. for advice and help on Passing .Net Interviews
.Net Projects
Best-of-breed application framework for .NET projects, developed by ExamGuru, Inc. and ExamGuru IT
Free .net Help
Commission ExamGuru, Inc. and his team for your next bespoke software project
FogBUGZ
The only bug tracking system carefully crafted with one goal in mind: helping teams create great software.
Awesome Tools
If you don't know about these, you're missing out... IT Certification Questions
IT Interview Questions
Free Oracle 10g Training
MCSE Boortcamp
Cisco Study Guides
Cheap Study Guides
Exact Questions
Dot Net Interview Questions
Oracle OCP
Cheap Travel
Designer Perfumes - Wholesale Prices
Free Programming Tutorials
 
ExamGuru IT Solutions - .Net Guru is owned and operated by ExamGuru, Inc., the man behind .Net Guru. If you're in the market for bespoke software or software consultancy, why not get him and his highly trained team to help? - www.examguru.net/ITCertification
 Copyright © ExamGuru, Inc. 2001-2006
Contact Us - Terms of Use - Privacy Policy - www.dot-net-guru.com - www.examguru.net - www.oraclesource.net - www.itinterviews.net - www.examguru.net/ITCertification