This is an automated email from the ASF dual-hosted git repository.
pstuedi pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-crail-website.git
The following commit(s) were added to refs/heads/master by this push:
new a4aae52 Fixing typo in YCSB blog
a4aae52 is described below
commit a4aae5212d8c89dc97568a7e00c1892456bda719
Author: Patrick Stuedi <pstu...@apache.org>
AuthorDate: Thu Oct 10 11:03:52 2019 +0200
Fixing typo in YCSB blog
---
site/_posts/blog/2019-10-09-ycsb.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/site/_posts/blog/2019-10-09-ycsb.md
b/site/_posts/blog/2019-10-09-ycsb.md
index ce9a588..b39054c 100644
--- a/site/_posts/blog/2019-10-09-ycsb.md
+++ b/site/_posts/blog/2019-10-09-ycsb.md
@@ -167,7 +167,7 @@ Besides update latency, we are also showing read latency in
the CDF figure below
When measuring the latency performance of a system, what you actually want to
see is how the latency is affected as the system gets increasingly loaded. The
YCSB benchmark is based on a synchronous database interface for updates and
reads which means that in order to create high system load one essentially
needs a large number of threads, and, most likely a large number of machines.
Crail, on the other hand, does have an asynchronous interface and it is
relatively straightforward to mana [...]
</p>
<p>
-We used Crail's asynchronous API to benchmark Crail's key-value performance
under load. In a first set of experiments, we increase the number of clients
from 1 to 64 but each client always only has one outstanding PUT/GET operation
in flight. The two figures below show the latency (shown on the y-axis) of
Crail's DRAM, Optane and Flash tiers under increasing load measured in terms of
operations per second (shown on the x-axis). As can be seen, Crail delivers
stable latencies up to a reas [...]
+We used Crail's asynchronous API to benchmark Crail's key-value performance
under load. In a first set of experiments, we increase the number of clients
from 1 to 64 but each client always only has one outstanding PUT/GET operation
in flight. The two figures below show the latency (shown on the y-axis) of
Crail's DRAM, Optane and Flash tiers under increasing load measured in terms of
operations per second (shown on the x-axis). As can be seen, Crail delivers
stable latencies up to a reas [...]
</p>
</div>
