This is old news, Apache *is* slow… It’s a comparision of nothing, SunOne is a special purpose webserver, while Apache is a “do everything” webserver.
No, it would be more interresting to have SunOne compared with for example AOLserver. Both are special purpose webservers targetted for the same job: serving havy traffic dynamic websites.
Unfortunately for Sun, AOLserver is free software and widely known as the fastest webserver in the world.
the version of sun one that i have runs on top of apache – how come sun one is pitted against apache?
sun one is designed to pit against ms iis, since the main component is chilisoft asp. the test should be serving up asp pages, not static pages, against ms iis.
the version of sun one that i have runs on top of apache – how come sun one is pitted against apache?
sun one is designed to pit against ms iis, since the main component is chilisoft asp. the test should be serving up asp pages, not static pages, against ms iis.
SUN One doesn’t run on top of Apache. Apache is included with Solaris by default but if one requires SUN ONE Webserver, you have to purchase it seperately.
Also, the Chillisoft plugged into Apache and SUN One Webserver.
the version of sun one that i have runs on top of apache – how come sun one is pitted against apache?
Assuming you were running SunONE WebServer, I was correct, it isn’t based on Apache. Why then bring up Chill!soft when what we are talking about is SunONE WebServer, which is the old Netscape Fastsite when then became iPlanet which then became SunONE WebServer and now it is something else again.
Not all web applications are location transparent — that is, they will scale up but they won’t scale out. So in some cases you are restricted to using just one application server. Those applications that can be scaled out can be scaled out just as easily on Sun ONE.
They used the jakarta connector 1 (jk1) and not the latest jk2, witch’s more faster and has loadbalancing features.
Why did you title your post “Coyote Connector for JSP”? Coyote isn’t a connector to the Apache webserver like jk1/jk2/webapp are… Coyote talks HTTP/1.1 protocol itself.
With Tomcat, you cand have one Apache and a lot of tomcat instances. With SunOne WebServer, you’ve got to have one instance, replied for all machines.
“Load balancing” in the mod_jk(2) sense is a rather primitive approach. The Sun Java Web Server can achieve both high availability and improved scalability across multiple systems by using clustering. If you’re a canonical round-robin load balancing advocate, you may want to read Zeus’s “Seven Myths of Load Balancing” paper:
> It’s a comparision of nothing, SunOne is a special purpose webserver, while Apache is a “do everything” webserver.
Sun ONE Web Server is no less general purpose of a web server than Apache. As apache it is capable of running CGI, PHP, ASP, JSP/Servlets. As Apache it can do reverse proxying, ULR-rewriting, authenication realms from different data sources and a ton of other stuff. Sun ONE is just a higher grade product than Apache, even though Apache is an excellent product in itself.
Why did you title your post “Coyote Connector for JSP”?
It was what the paper refers to.
The Sun Java Web Server can achieve both high availability and improved scalability across multiple systems by using clustering
Clustering is not load balancing. I’m using one solution where we have alteons for Apache and mod_jk2 for Tomcat. With Iplanet you cannot do that kind of load balancing.
For simple pages, practically any webserver can saturate the outbound network. Its nice to see people working on performance but it won’t put a dent in Apache’s market share.
For this same reason, kernel httpd type projects have gone nowhere. Once you have saturated the outbound traffic, any more performance is pointless.
> Clustering is not load balancing. I’m using one solution where we have alteons for Apache and mod_jk2 for Tomcat. With Iplanet you cannot do that kind of load balancing.
What makes you think that? I’m supporting a very high traffic web site using Alteons as load balancers and Sun ONE Web Servers behind them. Works like a cham. Also on the same note, you can use the Sun ONE Webservers as load balancers since nowadays Sun ONE comes with load sharing and load balancing plugins. Using Sun ONE Webservers as load balancers can actually proove much more economical and maintainable solution as compared to Alteon for instance.
meh, sponsored by Sun :/
serverwatch.com seems to say the somewhat same thing though, might be they have a good product on their hand
This is old news, Apache *is* slow… It’s a comparision of nothing, SunOne is a special purpose webserver, while Apache is a “do everything” webserver.
No, it would be more interresting to have SunOne compared with for example AOLserver. Both are special purpose webservers targetted for the same job: serving havy traffic dynamic websites.
Unfortunately for Sun, AOLserver is free software and widely known as the fastest webserver in the world.
They used the jakarta connector 1 (jk1) and not the latest jk2, witch’s more faster and has loadbalancing features.
With Tomcat, you cand have one Apache and a lot of tomcat instances. With SunOne WebServer, you’ve got to have one instance, replied for all machines.
the version of sun one that i have runs on top of apache – how come sun one is pitted against apache?
sun one is designed to pit against ms iis, since the main component is chilisoft asp. the test should be serving up asp pages, not static pages, against ms iis.
there’re SunONE* outthere. which SunONE product d’you run?
btw, it seems that Sun had changed their ‘umbrella’ name for software products to “Sun Java System <whatever”
http://wwws.sun.com/software/
the version of sun one that i have runs on top of apache – how come sun one is pitted against apache?
sun one is designed to pit against ms iis, since the main component is chilisoft asp. the test should be serving up asp pages, not static pages, against ms iis.
SUN One doesn’t run on top of Apache. Apache is included with Solaris by default but if one requires SUN ONE Webserver, you have to purchase it seperately.
Also, the Chillisoft plugged into Apache and SUN One Webserver.
The test was run on windows 2000.
I am running SunONE 4.0.
4. Installing Sun ONE Active Server Pages 4.0
———————————————————-
The setup program takes you through the steps required to
install Sun ONE Active Server Pages 4.0. As you perform the
installation you have many options to accept default
configuration settings, or to specify your own. The setup
program installs the following components on the target
Web server:
* Sun ONE ASP Server
* Sun ONE ASP Administration Console
* JRE 1.4 for Chili!Beans (the use of Chili!Beans is
optional)
* Sun ONE ASP SpicePack components
* Apache Web Server 2.0.43 DSO (preconfigured; optional)
The above is shamelessly lifted from the “quick start” document.
No, you claimed:
the version of sun one that i have runs on top of apache – how come sun one is pitted against apache?
Assuming you were running SunONE WebServer, I was correct, it isn’t based on Apache. Why then bring up Chill!soft when what we are talking about is SunONE WebServer, which is the old Netscape Fastsite when then became iPlanet which then became SunONE WebServer and now it is something else again.
Shows that a certain company I know, made a good decision even without knowing it. Hmmmm….
I have been working with the Netscape webservers since they were called Enterprise and FastTrack…. that’s almost 7 years. I never benchmarked them.
Not all web applications are location transparent — that is, they will scale up but they won’t scale out. So in some cases you are restricted to using just one application server. Those applications that can be scaled out can be scaled out just as easily on Sun ONE.
They used the jakarta connector 1 (jk1) and not the latest jk2, witch’s more faster and has loadbalancing features.
Why did you title your post “Coyote Connector for JSP”? Coyote isn’t a connector to the Apache webserver like jk1/jk2/webapp are… Coyote talks HTTP/1.1 protocol itself.
With Tomcat, you cand have one Apache and a lot of tomcat instances. With SunOne WebServer, you’ve got to have one instance, replied for all machines.
“Load balancing” in the mod_jk(2) sense is a rather primitive approach. The Sun Java Web Server can achieve both high availability and improved scalability across multiple systems by using clustering. If you’re a canonical round-robin load balancing advocate, you may want to read Zeus’s “Seven Myths of Load Balancing” paper:
http://www.zeus.com/about/wp/register.cgi
> It’s a comparision of nothing, SunOne is a special purpose webserver, while Apache is a “do everything” webserver.
Sun ONE Web Server is no less general purpose of a web server than Apache. As apache it is capable of running CGI, PHP, ASP, JSP/Servlets. As Apache it can do reverse proxying, ULR-rewriting, authenication realms from different data sources and a ton of other stuff. Sun ONE is just a higher grade product than Apache, even though Apache is an excellent product in itself.
Why did you title your post “Coyote Connector for JSP”?
It was what the paper refers to.
The Sun Java Web Server can achieve both high availability and improved scalability across multiple systems by using clustering
Clustering is not load balancing. I’m using one solution where we have alteons for Apache and mod_jk2 for Tomcat. With Iplanet you cannot do that kind of load balancing.
For simple pages, practically any webserver can saturate the outbound network. Its nice to see people working on performance but it won’t put a dent in Apache’s market share.
For this same reason, kernel httpd type projects have gone nowhere. Once you have saturated the outbound traffic, any more performance is pointless.
> Clustering is not load balancing. I’m using one solution where we have alteons for Apache and mod_jk2 for Tomcat. With Iplanet you cannot do that kind of load balancing.
What makes you think that? I’m supporting a very high traffic web site using Alteons as load balancers and Sun ONE Web Servers behind them. Works like a cham. Also on the same note, you can use the Sun ONE Webservers as load balancers since nowadays Sun ONE comes with load sharing and load balancing plugins. Using Sun ONE Webservers as load balancers can actually proove much more economical and maintainable solution as compared to Alteon for instance.