This brings up the question of /functional/ testing versus /performance/
testing. As long as the two types of testing are separated, then there
will likely be no complaints from developers and testers about using
non-Exadata Oracle database for non-prod environments.
/Functional/ testing is inexpensively and easily supported using
commodity or cloud servers, and for workload that is not offloaded to
cells there is no appreciable difference in performance. However, there
is no configuration of non-Exadata which can compete with Exadata for
workloads offloaded to Exadata cell storage, so /performance/ testing
must be on Exadata to avoid complaints from testers and developers.
Particularly tricky is when the database is "optimized" for Exadata cell
offload by the removal of indexes, making functional testing difficult
or impossible on non-Exadata. Since no COTS applications are assumed to
reside on Exadata, this form of optimization is always a local decision.
On 10/30/18 10:43, Ls Cheng wrote:
Hi
I have a customer has commodity servers for non-prod environments. He has been running with this setup in the last two years OK.
BR
On Mon, Oct 29, 2018 at 9:08 PM Chris Taylor <christopherdtaylor1994@xxxxxxxxx <mailto:christopherdtaylor1994@xxxxxxxxx>> wrote:
For you guys running Exadata, are you also running your non-prod
environments also on the same Exadata machine, or do you run them
on secondary commodity servers?
Our primary Prod DBs are VLDB and I don't *think* we're going to
want to stick our non-prod environments on the same Exadata machines.
But that means licensing a pretty big secondary commodity server
and potentially Actifio in the middle to handle the clones of the
non-prod environments.
Chris
