Oracle TimesTen Velocity Scale is based on a foundation of the TimesTen In-Memory Database. TimesTen has very low latency for SQL operations which are measured in microseconds.
It is hard to make apples-to-apples comparisons between databases as there are so many variables. When DB vendors benchmark each others products, there is always the suspicion that the competitors DB is not tuned optimally. The following is an example of an apples-to-apples DB benchmark:
In August 2016, Google published an OLTP DB benchmark for a high availability configuration between two Availability zones using the Sysbench DB read/write workload. Google optimized Google Cloud SQL Second Generation in Google Cloud and Google ran Amazon RDS MySQL and Aurora on AWS. A consulting firm (2ndWatch.com) soon re-ran the benchmarks showing that Amazon Aurora was not tuned optimally. 2ndWatch [with consulting from Amazon] was able to show that AWS Aurora was able to outperform Google Cloud SQL Second Generation. This meant that the DB vendors rather than Oracle verified that their databases were optimally tuned for this benchmark.
As this Sysbench read/write DB is doing synchronous replication between two availability zones [data centers], the network round trip time was the dominant factor for TimesTen Velocity Scale.