Hi,
Currently in 4.0 and 3.2 we do not have a way to adjust the default thresholds for storage.
In these releases these are currently set such that our customers experience is increased. By having better and predictable performance.
As you mentioned currently we only have the quotas on the individual groups, dsources or VDBs.
For completeness, here are the links to our docs which discuss these topics:
http://docs.delphix.com/display/DOCS40/An+Overview+of+Capacity+and+Performance+Information
http://docs.delphix.com/display/DOCS40/Setting+Quotas+and+Reservations
In terms of CPU and memory for the Delphix Engine, we have found that reserving the CPU and Memory on the ESX server for the Delphix Engine guest is a best practice and very much recommended.
Once you have created VDBs Delphix is acting as the storage for these VDBs and it is very important that the CPU is not taken away and/or the memory does not get swapped or ballooned out on the ESX side as this has caused serious issues for the Delphix Engine.
I just talked to one of our performance engineers and they will most likely be blogging about this shortly all going well.
You can find Uday’s blog here:
http://blog.delphix.com/uday/category/performance/">http://blog.delphix.com/uday/category/performance/">http://blog.delphix.com/uday/category/performance/
Currently we discuss CPU and memory here in our documentation, where our wording is “strongly recommend” and “required” for reservations on ESX:
http://docs.delphix.com/display/DOCS40/Virtual+Machine+Requirements">http://docs.delphix.com/display/DOCS40/Virtual+Machine+Requirements">http://docs.delphix.com/display/DOCS40/Virtual+Machine+Requirements