cancel
Showing results for 
Search instead for 
Did you mean: 

SAP BI4.1 DashboardsProcessingServer performance tuning

Former Member
0 Kudos

Good afternoon one and all!

Got a question regarding tuning the DashboardsProcessingServer on BI4.1.

Our landscape(new) is a cluster, 2 servers, SAP BI4.1SP5

I’ve seen plenty of info and white papers on tuning the APS, but nothing much on the DashboardsProcessingServer(or the DashboardsCacheServer).

At this customer, the DashboardsProcessingServer quite regularly halts, and is left in initialising state. Can’t restart it, so whole server needs restarting. My assumptions are the dashboards (multiple) take up too many system resources/memory, and eventually the Server becomes unstable, and halts.

In the Admin guide, the parameters are described as follows (limiting those that seem to have most impact and can be tuned best):

  • Maximum Concurrent Jobs
  • Specifies the maximum number of independent jobs allowed to run concurrently on the server. If the value of this property is set to “0”, the server applies a suitable value, based on the CPU and memory of the machine that the server is running on
  • Maximum number of Prestarted Children
  • Specifies the maximum number of prestarted child processes that are allowed by the server. If this value is too low, the server creates child processes as soon as requests are made, and a user may experience latency. If this value is too high, system resources may be unnecessarily wasted by idle child processes.
  • Java Child VM Arguments
  • Specifies the command-line arguments that a resupplied to child processes that are created by the server.

Now this last one I’m curious about, the default is:

Xmx858M,Dswfinjection.lang.directory=%CommonJavaLibDir%,Dbusinessobjects.connectivity.directory=%CONNECTIONSERVER_DIR%

So, who came up with 858M?? It doesn’t fit in line with 128,256, 512, 1024… etc etc?!

I’ve upped this value to Xmx2048M, and will run tests on the dashboards, see if this improves the stability of the server(s).

Any other recommendations on tuning this server further, or the reason we have this funny Xmx858M value??

Many thanks!

Rene

Accepted Solutions (1)

Accepted Solutions (1)

former_member194862
Active Contributor
0 Kudos

Definitely adding the memory i.e. increasing XMX helps.APS does not come in the workflow of the Dashboards.

Also we should not create too many Dashboard cache servers.

Answers (0)