How many managed servers and datasource in a domain WLSDM supports?

[whching]

Hi,

I have a domain with 60+ managed servers and 100+ datasources.
And I would like knowing if WLSDM support such a large scale deployment. As the original Admin Console is quite slow when with this kind of scale. Any reference with such scale in production deployment?

Regards,
Rock

[wlsdmsupport]

Hi Rock,

We have benchmark to support WebLogic domains that have 40+ ManagedServers and 50+ data sources. And all our page load is between 1-3 seconds for this domain and WLSDM perormed really well.

For your case; the most struggling thing is going to be completing WLSDM wizard; if you are enough patient wait for every step in the wizard process.

But, please first of all try it in your non-production environment.

We are ready to solve your cases and performance bottlenecks.

How many wlsdm_agent are you planning to install on managed servers?

Regards…

[whching]

Hi @wlsdmsupport

I am just start looking at WLSDM, what is the difference of having one agent per cluster against one agent per managed server?

BTW, where I could find the resource overhead when WLSDM is used on managed servers? say, how much more heap memory it will use and how about any extra I/O it would introduced?
Thanks

Regards,
Rock

[wlsdmsupport]

@whching said:

Hi @wlsdmsupport

I am just start looking at WLSDM, what is the difference of having one agent per cluster against one agent per managed server?

BTW, where I could find the resource overhead when WLSDM is used on managed servers? say, how much more heap memory it will use and how about any extra I/O it would introduced?
Thanks

Regards,
Rock

Hi,

1. If you have two member cluster and these members are on different machine then install two agent. If you have 4(four) member cluster and these members on two machine (two managed server per machine). Then install two agent (same with previous). Much agent, much traffic. Same behavior, same machine… Then go for one agent.

More information is available on README: http://www.wlsdm.com/docs/README#IV.Installation

2. WLSDM runs on AdminServer and you should not install any application on WebLogic admin console. So, it’s run-time console, should not affect your domain. WLSDM’s AdminServer overhead is negligible; one of the least overhead in the market; because we are not injecting any code to run-time classes. Maximum overhead for the managed server (considering backend monitoring is open) is about 3%-4%.

You had better, test on your current domain; because your domain is extra ordinary and you will see that WLSDM would be one of the best solution for this domain and its infrastructure.

Regards…