Personally, I have not experienced performance problems with this site. In fact, I have found the site to be quite speedy. But let's assume they do have problems. Why might they have problems, without considering the Java servlet/jsp architecture? 1. The new site just went live 3/1. Any new site redesign is bound to have problems, especially when you first start working with an unfamiliar technology (ie, servlets, jsp). 2. They did a mass mailing to their entire customer base informing them of the new site, and asking them to log on to register. If all your customers flood your site on the same day, you might very well not have accounted for that type of traffic. [There is something to be learned by this... stagger the notifications about a new site over several weeks.] I don't know whether they are experiencing problems with the servlet/jsp technology. I also don't know whether they are experiencing problems with their servlet/jsp engine (someone on this list said it is WebSphere). But I do know that you can solve most problems with CGI + a lot of servers. And I do know that servlets/jsp are far more efficient than CGI and can achieve a higher throughput than CGI. So, in general... servlets/jsp can serve the same volume fewer servers. As with any other computing problem, bad designs lead to poor performance.... usually it is not the tools, it is usually your application or system/network design. A servlet/jsp architecture doesn't get you out of the "how do I structure my back-end application" problem, which is usually where application performance problems lie. But servlets/jsp do give you a convenient way to write the front-end. I'm still interested in hearing about servlet/jsp performance, including any issues. But I have done enough load/scalability research to believe that the servlet/jsp "architecture" can be fast and scalable... and that many tools go a long way toward reaching the potential. I am very interested in hearing about the performance-oriented design choices that went into the servlet and jsp specifications. For example, servlets are stateless and multithreaded... because stateless components have been shown to be the best architecture for achieving high throughput. I would also like to know what optimizations are made by each vendor, and where improvements can be made. For example, I have been looking into JRun's implementation of JSP... and I can see several optimizations they missed in 2.3. For each line in the source JSP file, the generated servlet code writes a literal string; it would be more efficient to collapse consecutive lines into a single string or to read the .jsp file at init() time, and write regions from this file. And for JSP beans... JRun uses run-time introspection to create the bean and access bean properties; it would be more efficient to use compile-time introspection and generate the accessor code, avoiding the cost of introspection at run-time. That is what I'd like to see more of on this list... discussions of 1) how the specifications allow for efficiency, 2) how the vendors can improve their efficiency, and 3) how developers can make their own code more efficient. -eric Franklin Schmidt wrote: > > Eric R. Williams wrote: > > > > I have seen requests several times on SERVLET-INTEREST and > > JSP-INTEREST for information on commercial sites using > > servlets and JSP. > > > > Well, I just bumped into one and I thought people would be > > interested to know about it. > > > > It is http://www.americancentury.com/ > > The first line on this site is "We are currently experiencing sporadic > performance problems on our site". So I am not sure if this is a great > example for JSP. In fact, I would be very interested to know what is > causing their performance problems. > > And like several other people, I would be interest to know about any > commercial sites using servlets and/or JSP that are not having > performance problems. ___________________________________________________________________________ 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
