See below > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED]] > Sent: Monday, May 20, 2002 12:59 PM > To: 'Jetspeed Users List' > Subject: RE: Is Jetspeed appropriate ? > > > > Also : > > > > > > - Performance : All the jetspeed web sites I have seen were not > > > particularly fast. Is there any known issue WRT > performance ? Do all > > > the performance issues come from aggregated content or is the > > > Jetspeed framework itself (or > > > Turbine) a bottleneck ? Or is it Tomcat (does it make a > difference > > > running jetspeed on Resin) ? Is there any work going on at the > > > current time to improve performances ? > > > > > > > For the upcoming release, > > which is scheduled sometime this summer, right ? Any big work > remaining ? >
Yes, 'this summer' sounds just vague enough ;) See the TODO-RELEASE-1.4.txt in the root of cvs. > > we will tune Jetspeed for performance. > > Ive ran Jetspeed on Weblogic and other web servers. > > Im also running it on Apache with several Tomcat nodes. > > Have you seen noticeable improvements over Tomcat ? > Yes sorry to say. I don't want to go into comparing app servers though since I work in the application server biz... Recommend doing your own benchmarks > > I think performance is something we can improve on, and is > not a major > > issue. > > Meaning, you believe it is performant ATM or that it can be > easily be improved ? > It can be improved, hopefully easily, but its hard to say until you actually profile it. Part of the 1.4 release plan is to improve performance. > > > Issues: > > - there's a lack of diverse out of the box portlets. > > Yes, but I believe the most useful ones are there already, I > think. I think the biggest work is probably on SSO-enabling > the WebPage one. It would be nice to make sure that the JAAS > implementation is easily accessible from Portlets so that we > can plug-in authentication schemes for HTTP connections for example. > > > With the > > standardization of portlets coming soon, Jetspeed will be > able to use > > any standard portlet. > > Yes, but that's probably not soon enough ... We'll be in > production when this happens ... (if everything goes fine !). > It's not before Jetespeed 2.0, right ? And anyways, the JSR > is not yet finalized. It isn't finalized but it is coming along (Im on the expert group) We plan to base Jetspeed 2.0 on the spec. when it is available hopefully sometime later this year > > Thanks again David. > -Vincent > > > > > David > > > > > Lots of questions ... ! > > > > > > Thanks a lot for your help > > > -Vincent > > > > > > > > > -- > > > To unsubscribe, e-mail: > > > <mailto:jetspeed-user-> [EMAIL PROTECTED]> > > > For > > > additional commands, > > > e-mail: <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > > -- > > To unsubscribe, e-mail: <mailto:jetspeed-user- > > [EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:jetspeed-user- > > [EMAIL PROTECTED]> > > > > -- > To unsubscribe, e-mail: > <mailto:jetspeed-user-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
