You might be able to upgrade to WAS 6.1, which supports Java 5. This may be a less big hurdle for your company/client than upgrading a full major release.
/JK 2009/7/20 Kito Mann <[email protected]>: > Hello Shasi, > > Honestly, looking at your stack, I think you could gain the biggest > performance boost by either switching to JDK 1.5 or upgrading to WAS 7.0 > (which I'm sure isn't a trivial task politically). > > Upgrading to Facelets is a great long-term move, especially since JSF 2.0 > includes Facelets. It's pretty painless, especially if you're using the JSPX > syntax (which most people don't use). However, using Tiles complicates the > process, and it's certainly not something I would try with a larger app at > the last minute. > > So, read the articles I mentioned, follow the advice on this list in order > to find and eliminate bottlenecks, and try upgrading your JDK. > > On Mon, Jul 20, 2009 at 5:27 AM, Shasi Mitra Yarram <[email protected]> > wrote: >> >> Hi - This is my configuration >> 1.JSF1.1 >> 2.MyFaces 1.1.6 >> 3.Tomahawk 1.1.8 >> 4.IBM Websphere Server 6.0 >> 5.Ajax4JSF1.1 >> 6.JDK1.4 >> Somebody mentioned that using jsp as page description slows down >> performance. Instead use Facelets. Can you tell what he meant? >> Also our application has 447 jsp pages. We are using struts-tiles. If we >> want to convert to facelets how much time it'll take for the entire >> conversion , as its time for us to freeze the code. Is it easy to >> incorporate those changes? >> >> Thanks, >> Shasi >> >> --- On Sat, 18/7/09, Kito Mann <[email protected]> wrote: >> >> From: Kito Mann <[email protected]> >> Subject: Re: Performance issues with JSF >> To: "Shasi Mitra Yarram" <[email protected]>, "MyFaces Discussion" >> <[email protected]> >> Date: Saturday, 18 July, 2009, 7:47 PM >> >> Hello Sashi, >> >> Ok, but which version? I'm asking because I had a client that switched >> from WAS 7.0 on AS/400 to 7.0 on Linux and saw some major performance >> improvements. >> --- >> Kito D. Mann -- Author, JavaServer Faces in Action >> http://twitter.com/kito99 http://twitter.com/jsfcentral >> http://www.virtua.com - JSF/Java EE consulting, training, and mentoring >> http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info >> +1 203-404-4848 x3 >> >> >> On Sat, Jul 18, 2009 at 12:14 AM, Shasi Mitra Yarram >> <[email protected]> wrote: >>> >>> Thanks Kito Mann for the reply. I am using IBM's websphere server and >>> unix OS. >>> >>> --- On Fri, 17/7/09, Kito Mann <[email protected]> wrote: >>> >>> From: Kito Mann <[email protected]> >>> Subject: Re: Performance issues with JSF >>> To: "MyFaces Discussion" <[email protected]>, [email protected] >>> Date: Friday, 17 July, 2009, 4:27 PM >>> >>> Hello Shashi, >>> >>> A couple more recommendations: >>> >>> * Follow Dan Allen's suggestions in these articles: >>> http://www.jsfcentral.com/articles/speed_up_your_jsf_app_1..html and >>> http://www.jsfcentral.com/articles/speed_up_your_jsf_app_2.html. Often, as >>> someone else suggested, the problem is placing time-consuming code inside of >>> getter methods that are referenced via the EL. >>> >>> * Time different parts of the life cycle -- this will verify whether or >>> not the problem is really in the Restore View phase. You can do this by >>> writing a simple PhaseListener or using something like PrimeFaces' >>> FacesTrace (http://primefaces.prime.com.tr/en/). >>> >>> Which application server and OS are you using? >>> --- >>> Kito D. Mann -- Author, JavaServer Faces in Action >>> http://twitter.com/kito99 http://twitter.com/jsfcentral >>> http://www.virtua.com - JSF/Java EE consulting, training, and mentoring >>> http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info >>> +1 203-404-4848 x3 >>> >>> >>> On Fri, Jul 17, 2009 at 5:56 AM, Shasi Mitra Yarram >>> <[email protected]> wrote: >>>> >>>> Hi All - We have built a J2EE application with JSF (MyFaces, Ajax4JSF) >>>> ,Spring and IBatis. What we find is, each of the screen takes lot of time >>>> to >>>> load. We find no performance issue with Spring or Ibatis (after verifying >>>> via JProfiler). Jprofiler shows the JVM memory is occupied b JSF objects. I >>>> found that the screen loading is taking time for two reasons. >>>> 1.The JSF screens (which has cook menu) take time to load. >>>> 2.The overall screen painting in the browser takes time to load. >>>> Our JSF screens are not too complicated and even the simplest screen >>>> takes time to load. Note that each of the screens always loads JSCookMenu. >>>> We visited apache site for tuning JSF. As per their suggestion we did the >>>> following >>>> 1. We set the State saving mechanism as server side. >>>> 2. Serialization of session objects was set to false. >>>> 3. Compression of objects was set to false. >>>> 4. Streaming Add Resource and t:documentHead were added. >>>> But none of these improved the performance. >>>> The overall screen takes time and I'm wondering if we should do >>>> effective caching of images,CSS and js files. I visited plenty of websites >>>> and tried to move all these client specific files under the <head> tag, >>>> loaded the images via CSS but nothing helps. We have high capacity machines >>>> and I dont think desktop config is playing a role. >>>> We thought the problem could be bcos of network traffic or slow >>>> performance of underlying platform websphere server. We checked other >>>> application running in the same envrironment and they are extremely fast. >>>> The only difference b/n our application and the other is JSF. >>>> I'm short of solutions. Any valuable input will be greatly appreciated. >>>> >>>> ________________________________ >>>> Looking for local information? Find it on Yahoo! Local >>> >>> ________________________________ >>> Love Cricket? Check out live scores, photos, video highlights and more. >>> Click here. >> >> ________________________________ >> Yahoo! recommends that you upgrade to the new and safer Internet Explorer >> 8. >
