You need to determine what is causing the slow response. Below are some of the questions I usually ask.
o Has the servlet container been restarted since you changed the TR.p parameters? o Are their other application running on the server that compete for resources? o Are their enough system resource to run the servlet container and Jetspeed? This includes memory so the OS is not page swapping. o Has Jetspeed been up long enough for the portlets to initialize, this include retrieving the content. In some cases a portlet will not initialize until the first time it is accessed. o Is their a performance difference between a browser session originating on the Jetspeed server vs. a remove machine? If the local browser is OK but the remote is slow, then look at the network. o Is the servlet container responsive? Try running the included examples include with the servlet engine. If the sevlet container is responsive, then look at Jetspeed portlets Also please be define "very slow response time." This is very relative unless you include a measurement, like 5 seconds. Paul Spencer Pramod Jain, INDENT wrote: >I just installed jetspeed and loaded up the demo page and got very slow >response time. > >I tried the following (recommended under topic "jetspeed=slowspeed"), but >still get the same response time: > > > >>-- change all logging levels in the >>~/WEB-INF/conf/*.properties files to be INFO instead >>of DEBUG >> >>-- give Tomcat a lot of memory via the >>CATALINA_OPTIONS. e.g. -Xmx256m and -Xms128m >> >>-- look for velocity caching options in >>TurbineResources.properties and turn it on >> >> >> > >Would appreciate any help in getting decent response times. >thanks > >pramod > > >-- >To unsubscribe, e-mail: <mailto:[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]>
