nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Performance Throttling in OpenDeploy 6.1

System

Hello everyone,

This is a followup to the devnet presentation this morning. There were some details on the performance throttling feature that I had to check on.
The thottling feature allows you to scale back concurrent deployments depending on adjustable thresholds (file descriptors and disk space in this release, additional tunings to come in the future).

For the 6.1 implementation, notification will be in the logs and new deployments will be cancelled not queued up. As we move forward, we'll continue to build on this, adding more enhancements.

Mariam

Find more posts tagged with

Comments

jed

Will OD return a specific return code or output to STDERR? This way, if a wrapper script is invoking OD, the deploy can be auto-retried after a set time.

Also, will there be any way to query OD to determine how many legs are currently being used?

--
Jed Michnowicz
jedm@sun.com
Content Management Engineering
Sun Microsystems

Migrateduser

Hi Jed... response from engineering is below. I'll file feature requests for your enhacements. This is a first cut at throttling, geared more to prevent process hangs. I can see us beefing this up in future releases.

Mariam

Will OD return a specific return code or output to STDERR? This way, if a wrapper script is invoking OD, the deploy can be auto-retried after a set time.
[Vijayakumar Kothandaraman] No specific return code for throttling failure

Also, will there be any way to query OD to determine how many legs are currently being used?
[Vijayakumar Kothandaraman] We do log the deployment legs in the log file but no CLT ..