You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@crail.apache.org by ps...@apache.org on 2019/10/10 09:04:32 UTC
[incubator-crail-website] branch asf-site updated: Publishing from
a4aae5212d8c89dc97568a7e00c1892456bda719
This is an automated email from the ASF dual-hosted git repository.
pstuedi pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-crail-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new edb3730 Publishing from a4aae5212d8c89dc97568a7e00c1892456bda719
edb3730 is described below
commit edb37304303e02a0e86fa3ffa9008459e0f15b03
Author: Patrick Stuedi <ps...@apache.org>
AuthorDate: Thu Oct 10 11:04:17 2019 +0200
Publishing from a4aae5212d8c89dc97568a7e00c1892456bda719
---
content/blog/2019/10/ycsb.html | 2 +-
content/feed.xml | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/blog/2019/10/ycsb.html b/content/blog/2019/10/ycsb.html
index 10c554d..1f8efdc 100644
--- a/content/blog/2019/10/ycsb.html
+++ b/content/blog/2019/10/ycsb.html
@@ -230,7 +230,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>
diff --git a/content/feed.xml b/content/feed.xml
index 115ebe8..b00704c 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.8.5">Jekyll</generator><link href="http://crail.incubator.apache.org//feed.xml" rel="self" type="application/atom+xml" /><link href="http://crail.incubator.apache.org//" rel="alternate" type="text/html" /><updated>2019-10-10T11:01:13+02:00</updated><id>http://crail.incubator.apache.org//feed.xml</id><title type="html">The Apache Crail (Incubating) Project</ti [...]
+<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.8.5">Jekyll</generator><link href="http://crail.incubator.apache.org//feed.xml" rel="self" type="application/atom+xml" /><link href="http://crail.incubator.apache.org//" rel="alternate" type="text/html" /><updated>2019-10-10T11:04:15+02:00</updated><id>http://crail.incubator.apache.org//feed.xml</id><title type="html">The Apache Crail (Incubating) Project</ti [...]
<p>
Recently, suppport for Crail has been added to the <a href="https://github.com/brianfrankcooper/YCSB">YCSB</a> benchmark suite. In this blog we describe how to run the benchmark and briefly show some performance comparisons between Crail and other key-value stores running on DRAM, Flash and Optane such as <a href="https://www.aerospike.com">Aerospike</a> or <a href="https://ramcloud.atlassian.net/wiki/spaces/RAM/overview">RAMClo [...]
</p>
@@ -151,7 +151,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>