I think it has nothing to do with the portlets since the only changes he (Dan) made was the number of users. I suggest to do some profiling (both IBM and Oracle stuff can help ) to the jetspped instance to see what is going on. I used to work on J1 last year and I did found some scalability issues on it. I donno if they still exist on not.
Regards , On Mon, 15 Nov 2004 18:15:49 -0800, David Sean Taylor <[EMAIL PROTECTED]> wrote: > Hi Dan, > > Try having zero portlets on the default page, and see if it makes a > difference... > > Then start adding your portlets in and see where the bottleneck starts. > > > > > Dan Moore wrote: > > > Hi folks, > > > > I have an application I'm building on top of Jetspeed 1.5--I just > > grabbed the WAR from portals.apache.org. The back end is an Oracle > > database. > > > > I end up having around 100,000 users in the turbine_user table. All of > > these users have the same PSML and they all have the same role; we're > > using the role fallback mechanism. The PSML is stored on the > > filesystem, under role/user/<language>/<country>; right now I'm only > > using English and the US. > > > > I was seeing a massive slowdown in our application when we went from > > the 3 sample users to the full 100,000, so I'm trouble shooting that. > > The average page draw went from 4 seconds to 18 seconds (this is with 4 > > simulated users hitting the home page at once). I was able to get > > response times of around 4 seconds on my box (it's old and slow) with > > the default jetspeed setup (just as downloaded from the site: > > hypersonic db, only logging in as an anonymous user). > > > > I modified the JetspeedSessionValidator to log folks in with a cookie, > > but that's the only code change I've made to the vanilla jetspeed war > > I'm benchmarking (I profiled it and that method only adds 300 > > milliseconds or so). I did make two configuration changes: > > > > automatic.logon.enable=true > > > > database.default.maxConnections=20 > > > > I took a look at this page: > > http://nagoya.apache.org/wiki/apachewiki.cgi?JetspeedPerformanceTips > > but didn't really notice any huge gains (I did up the number of > > connections allowed in TurbineResources.properties and > > Torque.properties). In addition, it seems that many of the suggestions > > have been incorporated into the defaults. > > > > The turbine_user and turbine_user_group_role tables have their standard > > indices. > > > > I'm trying to figure out where the extra 15 seconds comes from. I > > guess I'm not so concerned about the absolute time it takes (we're > > going to deploy on much faster hardware), but I do want to get the > > ratio down. > > > >>From just watching the page draw, it seems that the top gets drawn > > quickly, then the actual portlets themselves are slow. I see warnings > > in the logs about the specific psml files not being found for a given > > user--are these a significant slowdown? Should I change > > services.Profiler.fallback.country > > and > > services.Profiler.fallback.language > > to be false? > > > > For one PSML file, is db based PSML a better choice? Is there some > > caching that I can turn on that isn't on by default? Is simpler PSML > > going to cause any kind of speed up? > > > > I also searched the mailing list for performance related issues. I saw > > this > > (http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgId=1640251) > > which I plan to try tomorrow morning, but didn't see any other things I > > should be doing. > > > > Any help would be most appreciated. > > > > Thanks, > > Dan > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > -- > David Sean Taylor > Bluesunrise Software > [EMAIL PROTECTED] > [office] +01 707 773 4646 > [mobile] +01 707 529 9194 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Regards, Youssef --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
