i have one query does Active Server Pages serve the request using thread.
i.e. for different request a new thread is created not a process like CGI?
-----Original Message-----
From: Nic Ferrier [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 30, 2000 10:55 PM
To: [EMAIL PROTECTED]
Subject: Re: highly scalable network server app
>>> skeptical <[EMAIL PROTECTED]> 30-Aug-00 6:07:03 PM >>>
>i also love the concept of java's write once run anywhere.
>my impression is that it's not very scalable.
This is not *really* on topic but it's close enough for me to answer
without annoying everybody here.
>my company recently wrote a client server app.
>we wrote the app server which services about 10k tcp
>connections with incoming requests for a sql server.
You'll have to be more specific... what do you mean by 10K requests?
Is this concurrent requests or is it something layered on top of a
persitent TCP connection?
>under our stress test with 10k users,
Again - is this concurrent "users" (a rather nebulous concept) or
requests? or TCP connections/sessions? or what?
This list focuses on servlets which are based on the HTTP protocol
and therefore we talk about:
- a request being an HTTP request
- a user being some concept that involves a number of requests tied
together with some timeout concept
- a session is a particular form of user connectivity, again
involving a number of requests.
In TCP general one talks about a TCP session as being the same as a
TCP connection.
In HTTP though TCP connections are (conceptually) only extant for the
life of a request and therefore we don't talk about the quality of TCP
connections much.
I think you'll find that Java's network IO is as good as NTs,
depending on the platform on which you run Java of course.
>if i were to do this with java, 1. how will i write the code?
Well - that's a question that can't really be answered. You haven't
given us enough details of your system and anyway we're not paid to do
your design work for you /8->
>2. what hardware do i need in order to achieve
>the same performance?
As I say... you haven't really specified the performance so it's hard
to say.
In general with network servers the performance issue is not socket
IO but thread performance. Java's thread performance is a lot better
than NT generally - this is why Java *can* challenge NT for server
side work (otherwise no one would be doing it right?).
If you look back through the archives of this list you'll find quite
a few case studies of using servlet engines to run big sites. Since a
servlet engine is basically just a multi threaded network server
that's an indication that the sort of thing you're talking about can
easily be done in java.
Nic Ferrier
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
