on 11-08-2016 2:48 AM
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):
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.