Justin Parisi

We've had to separate the performance side and the capacity and, you know, alerting side, and they've been two separate instances together.

Recently, we were able to combine them into a single pane of glass, but you still had to run two separate OVAs, right?

You still had to spin up two different machines.

So let's talk about on-command Unified Manager 7.2 and the feature that I have heard of most and that I am excited about, the actual real-life unification of Unified Manager.

So let's talk to Philip about that.

So tell us a little bit about those performance improvements.

What did we do to make that a little more peppy?

Have we changed any of the actual interfaces in terms of how we're writing the code?

I mean, have we gone from something like Java to HTML5 or something along those lines?

No.

And what about the database?

I mean, I know previously with like Data Fabric Manager, which is basically its grandfather, it was running on a Sybase database.

Are we still using that or are we using something else?

Previously with Sybase, I mean, I used to work in support and I used to deal with DFM issues, and Sybase was always kind of the issue because it couldn't scale, right?

It wasn't meant for large enterprise environments in some cases.

So with this database that you're using now, I imagine it scales better, especially now that we've merged the tables together and we have fewer tables to deal with.

Could you expound a little bit about that?

This optimization, is it also taking some pressure off of the cluster itself?

I know the MGWD process handles a lot of those ZAPI calls.

So are we sending these in parallel?