I appreciate your feedback, but I think you're confusing some of the
information presented. Solaris was on *Sparc*, although everything else
was. It wasn't comparing exclusively x86, and I'd certainly agree that
a Solaris Sparc (running a non-final release of JDK 1.2) performed
better with high connection loads, but I only have one Ultrasparc
sitting around. The article also showed that while IBM OS/2 JDK 1.1.7
had the highest *transaction rate* at 300 connections (the first chart),
it could not support more than 600 connections (the second chart).
I have 2 linux-alpha machines, one of them got converted to nt/alpha
because of effectively no java support (the link to the linux-alpha port
was dead). It's also still only 1.1.5, and I don't know even with Sun's
support whether we'll ever see a solid 1.2 port of the JVM for
linux-alpha. To me, x86 are the highest value machines around their.
They're too power hungry for PDA like devices, but if we can get SMP and
clustering working easily in a linux environment, there's the best way
to build a great system!
As for developing "who cares what machine, you don't have those stress
levels," does that mean you're suggesting I develop on linux and deploy
on NT? ;) I think you'd agree it's better to develop on wintel (or
something else if you want) and deploy on solaris or linux.
TowerJ looks very promising, but only once it reaches 3.0. To me, one
of the most powerful features of Java is dynamic class reloading (like
you do all the time with servlets and JSPs), and TowerJ 3.0 coming out
late spring/summer should have that. Then I'll even pay for it! (not
that the Volano tests showed any kind of stability with a high number of
connections).
I'm also eagerly awaiting the 2.2 kernel to be widespread (I'm just
using RH rpms since I don't have the time to rebuild the kernel or
research what point release is best for me right now). That will
hopefully solve the file-handle issues.
Linux has made a big splash because of its technical merits. Let's
leave the emotion-laden bashing to the Mac brown shirts with their
"color computers."
Serge Knystautas
Loki Technologies
http://www.lokitech.com
Ron Burton wrote:
>
> Id say the article showed Solaris as the best platform for development and
> distribution. With Linux and TowerJ or IBM OS/2 a good second. Nothing in that
> article showed NT as having any advantage at all.
>
> Be that as it may it does clearly show Solaris is the premier high volume server
> with IBM and NT way behind.
>
> As a developer who cares what platform you develop on, Like you really run 2100
> connection in the development environment. Also don't be too quick to judge, all
> the servers tested were Intel based. That in its self makes the entire report
> less than useful when considering the concepts of salability. Again it is far
> easier to migrate from Intel with Solaris and Linux to a more powerful UNIX based
> platform than NT.
>
> Ron Burton
>
> Serge Knystautas wrote:
>
> > I hate Microsoft as much as the next self-respecting developer, but as a
> > Java developer, Sun has unfortunately made NT the best Java platform
> > (since this is the JServ mailing list). Check out the latest Volano JVM
> > stress tests (I think this has already been mentioned on this list, but
> > you should review the results).
> > http://www.javaworld.com/jw-03-1999/jw-03-volanomark.html?022399txt
> >
> > Highlights include several JVMs on NT able to support up to 2100
> > simultaneous connections without choking, but Linux caps at 250
> > (roughly) because of file system sharing. Nevermind that the JITs on
> > Linux are less developed and stress-tests, so the performance is better
> > on NT. Better performance and scalability on NT. Never thought I'd say
> > that. That's the whole reason we're migrating so many other services
> > here to Linux (DNS, mail, dhcp, etc...).
> >
> > Sorry, but like I said, I'm stuck with Windows because of Java...
> >
> > Serge Knystautas
> > Loki Technologies
> > http://www.lokitech.com
> >
> > Ron Burton wrote:
> > >
> > > "Marc A. Saegesser" wrote:
> > >
> > > >
> > > >
> > > > There may be problems making CGI and servlet output unbuffered, that's why
> > > > I posted. If unbuffered CGI and servlets won't work then the only choice I
> > > > have left is to switch to a different web server for the Win32 platform.
> > >
> > > There is always the other alternative. :-)
> > >
> > > Sorry couldn't resist the temptation on this.
> > >
> > > Why would anyone use NT as the server anyway? Its expensive, slow and
> > > comparably unreliable.
> > >
> > > If there is some service that requires NT, use NT for that. However, the
> > > web server could run on any platform and still communicate with the service.
> > >
> > > I know this is not really helping allot, but often we tend to start down a
> > > single path convinced its the only one. Only to realize far to late we are on
> > > the wrong path.
> > >
> > > Ron Burton
> > >
> > > ----------------------------------------------------------------
> > > To subscribe: [EMAIL PROTECTED]
> > > To unsubscribe: [EMAIL PROTECTED]
> > > Archives and Other: <http://www.working-dogs.com/>
> > > Problems?: [EMAIL PROTECTED]
> >
> > ----------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
> > Archives and Other: <http://www.working-dogs.com/>
> > Problems?: [EMAIL PROTECTED]
>
> ----------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://www.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
----------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://www.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
