-
1. Re: reload of portlet definition from database causes performance problems
theute Mar 1, 2012 10:00 AM (in response to pschebezin)What do you mean by "reload of portlet configurations" ?
-
2. Re: reload of portlet definition from database causes performance problems
pschebezin Mar 1, 2012 10:42 AM (in response to theute)Hallo Thomas
Thank your your quick response.
We started the SQL Server Profiler to see, what activities are done and so we detected, that a lot of statements in the jdbcjcr-database are executed. While executing these statements the portal server gives no response to the users. This behavior is to be seen every 5 to 10 minutes and takes up to 20 seconds (until the user gets response from server). I only guess, but I think after getting information from jdbcjcr-database the portal- or portlets- configuration is newly built up and cached. Between the "reloads of portlet configuration" there are no performance problems.
Regards
Falk
-
3. Re: reload of portlet definition from database causes performance problems
pschebezin Apr 24, 2012 2:53 AM (in response to pschebezin)I found out, what to do...
The problem is the jdbc driver of MS SQL Server. It has as default parameter "sendStringParametersAsUnicode=true". This causes, that no index can be used. Always there is a full table scan. So in a large configurations the are horrible caching response times.
We set this parameter to false for jcr and idm ( e.g. gatein.jcr.datasource.url=jdbc:sqlserver://databaseservername;database=jdbcjcr_${name};sendStringParametersAsUnicode=false). The starting time of gatein went down from 2 mintes to 1 minute. And now it is possible to show the whole system to the users.