Hi, Danielle

We also did experiments to access random blocks of 500 times,

the results seem like more stable, most of the latencies are 10-30 ┢s and the maximum is 284 ┢s.

We have tested the random method many times and each experiment has similar results.

We wonder that why these same mechanisms, e.g., GC, journaling and checkpointing, cause different influence between the random and consecutive accessing?

Thanks a lot.

At 2017-08-01 16:05:54, "Danielle Costantino" <dcostantino@vmem.com> wrote:

What you are observing is the characteristics of how the drives firmware handles writes. This can be from write amplification caused by the drives GC, and journaling + checkpointing. This behavior may vary greatly between vendors and even firmware versions.

- Danielle Costantino

From: SPDK <spdk-bounces@lists.01.org> on behalf of 뇨 <cjj25233@163.com>
Sent: Tuesday, August 1, 2017 12:58:33 AM
To: spdk@lists.01.org
Subject: [SPDK] A issue about maximums of write latency when we access the same block consecutively.

Hi, all

Recently, we use a demo to obverse the latency.

We find that when we access the same block consecutively, the occurrence of maximum latencies will become more frequent.

Additionally, they can reach even 2-3 ms and present a periodical change.

Why?

(1) For the same block, the latency of the first accessing is about 10-12 ┢s while the second, third

and the forth accessing can reach 700-900 ┢s even 2-3 ms?

I want to know the reason why the operation difference between the first accessing and the others exists.

(2) Why the maximums of 2-3 ms have a periodical change?

Best wishes,

Jiajia Chu