Maximum number of system profiles for DT 6.x

What is the maximum number of profiles DT 6.x can support?  A few years back, we tried to break out our agent groups to more defined applications via profiles that only contained systems that interacted with each other and the DT server couldn't handle that many profiles. If we recall correctly we were told 20 to 25 was a reasonable max, so we were forced to group many things together. With the newer s/m/l/xl size settings has this changed?  Is the number of system profiles obtainable different for the various size settings (i.e. is it CPU/memory/disk that is the limiting factor or is it an application limited factor)?.  We want to be able to break up our hundreds of applications/agent groups into smaller profiles. 

We are trying to figure out if we are better off doing more smaller DT servers (which makes tracking purepaths across DT servers harder) or going with our preferred method of using XL systems with lots of profiles.  With advances in SSO, ESB and increasing service calls between applications the cross talk between the agent groups increases, which is a driver for using as few DT servers as possible (even with XL systems we need more than one). 

Hi

The current number on this is still 20-25. Why? Because we have to do certain housekeeping things for each system profile which consumes resources. We are working on improving this for the upcoming 6.3 (Fall 2015) Release.

Andi

Andi could you provide some details on the impact of having more system profiles.

Our setup in a perf testing environment require us to have many profiles. We have ~100 profiles and at given time ~30 profiles are active.

-Sreerag

Thanks for the info that will help with our planning.