This ain’t your grandpa’s job scheduler!
We’ve been working on redesigning and rewriting the Flux Operations Console from the ground up. It’s designed to be responsive and scale well to provide you with the latest runtime stats on your distributed enterprise jobs in one central webapp.
Here’s a quick video (1 min 26 secs) that illustrates the performance and scalability of the new Ops Console:
Flux Operations Console Performance Video
This video was taken when around 6,000 flow charts were running in the cluster and a background thread was adding flow charts constantly. Google Chrome on Mac was used for the browser.
Still using cron, Autosys, CONTROL-M, Quartz? Does the new Flux Ops Console make you jealous? 
Posted on September 2, 2010, in Uncategorized. Bookmark the permalink. 3 Comments.
This video was taken when around 6,000 flow charts were running in the cluster and a background thread was adding flow charts constantly.”
1. What kind of cluster is this ?
2. Where can we look at the engine’s performance stats instead of the web console’s ? The web console is only as responsive as the engine. Is that right ?
I know it seems like the Operations Console would only be as responsive as the engine, but that’s not entirely the case.
This video is showcasing the performance of the web tier: HTML, CSS, JavaScript, and REST. Things like page/tab switching, pagination, etc. were a sluggish in older versions of the Operations Console. These web application performance problems are eliminated in Flux 7.10.
The Flux 7.10 Operations Console also utilizes a distributed cache to monitor the status of flow charts in the cluster. Flux 7.9 used to query the database directly for status of flow charts. Flux 7.10 shows the real-time status of flow charts without contacting the database. This could allow the Operations Console to perform faster than the engine.
We made a few architectural changes in Flux 7.10 to make it perform faster both on the engine side and Operations Console side. The performance gain for both over Flux 7.9 is tremendous.
Flux does not provide any way to monitor the performance of a Flux engine, short of throughput of flow charts. Performance for Flux means “how many of your business processes can be executed in a given time?”. This can be measured through the run history API on the engine.
Pingback: Flow Chart Dependencies with Flux 7.10 « Nick @ Flux