CMS load balances WEBI report server requests?

[Former Member]

I have 2 CMS servers and 8 WEBI report servers on windows. Most reports are run-time query execution. When there are a lot of concurrent users, I notice the memory footprint is very uneven. One webi server is at 1.4G (max) while some other ones are barely at 300M. Does CMS do round-robin load balancing among webi report servers? How does CMS decides which webi report server to use? Thanks.

[Former Member · Accepted solution]

As far as I can tell, there is no intelligence to the "load balancing" at all. It seems to use your server until it can take no more and then assign to the next one.

If it is a "canned" query they are running, that report/query can be assigned a default server. You do this in the CMC by selecting the report and under properties, assign default servers under "scheduling server." There you can pick either to give preference to certain servers or to only use certain servers. This will allow you to distribute your heaviest reports to your strongest server.

Otherwise, under your server properties, you could reduce the number of connections allowed to force it to even out more. I think the webi server defaults to allowing 50 connections but it really can't handle more than 20 well. Lower that and it will push your reports out to the others much better.

[Former Member]

Hello,

A few months back I investigated the same issue for an old client and the reason for the "uneven" load balancing could be that one server is dealing with a very large/complex report while the other one is dealing with a much smaller/less complex report.

In terms of round-robin load balancing, BO doesn't support this yet as far as i'm aware.

I hope this helps.

Edited by: Rim Geurts on Aug 11, 2010 10:46 PM

[former_member208901]

How can we check Memory consuming by a WEBI Processing Server?

[Former Member]

Use your task manager and check memory of the webi report process...I agree that CMS is not doing round-robin. If you are not using server group, it is sending all requests to a default webi server, till it can't handle anymore. All in all, reduce maximum connection is probably the best thing to do for now....