This is the fourth part of this installment, comparing the performance consistency of the DBaaS cloud offering with a dedicated physical host. This time the previous read-only test was modified to be a 100% update read-write test. So every row read was updated in the following way:
begin
loop
for rec in (
select /*+
index(t_o)
*/
id_fk
from
t_o
) loop
update t_i&tabname t_i
set n = rec.id_fk
where id = rec.id_fk;
end loop;
insert into timings(testtype, thread_id, ts) values ('&testtype', &thread_id, systimestamp);
commit;
end loop;
end;
/
DBaaS:
Physical host:
Again the graph is supposed to show how many of the runs deviated how much from the overall median runtime. Again the DBaaS service shows a significantly different profile, but this time performed more consistently than in the previous read-only test - the probable reason for the difference will be explained in a later part of this series. The DBaaS service this time had some extreme outliers (max. > 160 percent deviation) that I didn't include in the graph to not distort the graph too much - but it were just a few runs out of more than 25.000 that were affected.
The same data on per day (per hour for the physical host) basis:
DBaaS:
Physical host:
As mentioned above the physical host data covers only a few hours and hence can't really be compared to the DBaaS data covering more than a week of data.
Finally the individual thread performance:
DBaaS:
Physical host:
Both environments show pretty stable run times per thread over time, and the graphs confirm what is mentioned above: The physical host this time outperforms the DBaaS, however, as already mentioned, a slightly unfair comparison as the physical host didn't had to read and write encrypted blocks.
The next parts will cover comparisons to other cloud providers.
Full name
Randolf Geist
My company
http://www.oracle-performance.de
Recent comments
1 year 45 weeks ago
2 years 5 weeks ago
2 years 9 weeks ago
2 years 10 weeks ago
2 years 15 weeks ago
2 years 36 weeks ago
3 years 4 weeks ago
3 years 34 weeks ago
4 years 18 weeks ago
4 years 18 weeks ago