Not exactly. Given enough time and a lot of hard disk, you can put the entire 1.9B triples into any database -- that doesn't prove that it scales. Also, if the database uses a single global mutex lock for all reads and writes, again it's not a scalable architecture.
Scaling is about throughput and latency. This post is trying to determine whether adding more machine power actually lets the db perform better.
Re:Scaling nodes in a Dgraph cluster
by LoSboccacc on Tuesday June 21, 2016 @08:57AM
(#11945261)
> Scaling is about throughput and latency.
under reasonable constraint. throughput and latency from a cacheable dataset is moot for big data.
I don't follow. Wasn't using as much data as possible exactly what scaling is about?