Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
limits for OpenDeploy 5.6
swong74
Hello,
I read somewhere that there was a limit of 50 legs to OpenDeploy. I think it was for version 5.5.1. Does that still hold true for v5.6sp1? Inasmuch as I don't foresee more that one to five people simultaneously running a deployment simultaneously, it is possible to have a few that are big enough to complicate/add to the smaller ones. E.g. each deployment has 5 receivers ... thus, that counts as 5 legs correct? So, say worse case, 10 big deployments are running to 5 receivers each, that makes it 50 legs. Assuming these big deployments were kicked off at the off-hours but have run a little longer to the primetime; now we have 4 groups ready for deploying ... will they be able to without adverse impact? Network traffic excluded of course.
Thanks.
Find more posts tagged with
Comments
Adam Stoller
The limitation is largely based on file descriptors used for all the different logs created by OpenDeploy and the JVM / Jave RMI stuff (and perhaps piped/socketed communications?).
I believe the limitation is still essentially there - but you might be able to get further using the iwodcmd CLT in 5.6 SP1 as it eliminates the separate JVM for each invokation - but I don't know whether or not this really helps in that regard.
--fish
(Interwoven Senior Technical Consultant)
swong74
Please elaborate on iwodcmd CLT and how it helps. Thanks.
Migrateduser
There are a couple of issues at play here. First is the number of concurrent legs that an OD base server or receiver can safely handle. The recommended limit of 50 has been replaced in OD 5.6 SP1. Please check out the release notes on p. 45: "Certified Limits for Number of Deployment Legs".
Another issue is that each invocation of an OD CLT incurs the processing overhead of starting up a new JVM. This can be problematic when invoking lots of deployments in close succession. The new iwodcmd CLT is a lighter-weight alternative to iwodstart, iwodschedadd, etc. Please see the OD 5.6 SP1 Release Notes, p. 36: "iwodcmd Command-Line Tool".
Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e:
tscallan@interwoven.com