Mike McElligott wrote:
>
> Hi all. I've seen this thread before, but in the posts I've read it never
> really got answered. My understanding is that ASP is compiled via C++ and
> that JSP is, of course, interpreted. Does anyone have numbers on what the
you must be JOKING!!!! (sorry :) )
If you rewrite that as:
>My understanding is that JSP is compiled via Java and
>that ASP is, of course, interpreted.
you have it about right.
> actual performance differences are? If ASP is significantly faster than JSP
> it's going to be hard to sell it to the shop I currently work for, but if
> JSP is faster it'll be a terrific excuse to do some fun stuff (read Java
> stuff). I can't imagine how JSP *would* be faster than compiled ASP - I'm
> just hoping I'm wrong. :) Does anyone have numbers?
Nope, no numbers, but here's my take:
(just as a background, I've been using JSP for about 2 months now, and
before that, ASP for about a year. I dont think I'd EVER go back to ASP)
JSP is Java, thru and thru. Its 'compiled' to a bytecode class, and if
you are running a JIT compiler (as I am), its effectivly native code.
Its quick as hell, and beats the crap out of ASP in 99.9% of cases.
ASP is 'compiled' in a way, I'd go with 'tokenized' personally. Its
definatly NOT compiled into C++ - for a start, that would be way too
slow, as compiling C++ is a dog at best, and a trip to the coffee
machine at worst. A lot of the objects you use (session, application,
request etc) are all C++ (I assume) as they are just ActiveX objects.
You can write them in any activeX-capable language if you want -
Delphi4, C++Builder4, VB6, VC++, VisualJ++, PowerBuilder???
AFAIK, its put into an intermediate state (higher level than bytecode)
and interpreted. Hell, its the exact same engine that IE, MS Office, etc
uses, and both of them are a long way from efficient. (VBScript, part of
the active scripting suite - you can build it into your own app if you
_really_ want)
Speed comparisons: JSP on my laptop (PII 266, 144meg RAM, Borland JIT
compiler) is maybe 2x the speed of ASP on my old works server (PII 350,
128meg RAM, IIS4). I dont have a precise metric, but it FEELS a lot
quicker.
Initial hit: I find them both to be about the same, which is quite a
credit to JSP, as it actually compiles it!! AFAIK, this is using the Sun
internal Java compiler, which I'm told is NOT quick.
> One other item: some of the team here believes that ASP chunks when too
> much session is used. Does anyone know if JSP suffers from the any session
> problems? Or which implementation is the most scalable?
Just by the fact that JSP will run on platforms other than NT, JSP wins
hands down. NT does not, and WILL NOT scale beyond about 200 users (quad
PII/Xeon, 1gig RAM is about the most you can get, and a dual UltraSPARC
should beat this hands down)
I dont know the internals of the sessions, but its the same as the
servlet sessions, and from what I can get, its just a holder for
classes. Do a
session.invalidate();
and you release all your session-held objects. V.cool for me :) MS says
not to use the session object for holding objects, as they dont get
released when the session dies - in JSP they do, as the reference gets
release, then the JVM garbage collects it....
I'd go with JSP, using something like JRun - you can then run it on NT,
Linux, Solarus etc etc, and even change your JSP 'engine' if you want (I
started with JRun, switched to web sphere, then to the sun reference
implementation, and I intend to move back to JRun for deployment)
Nic.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
