IntenseFinance/nosqlbench
3
0
Fork 0
mirror of https://github.com/nosqlbench/nosqlbench.git synced 2025-02-25 18:55:28 -06:00
Code Issues Packages Projects Releases Wiki Activity

minor docs update

Browse Source
This commit is contained in:
Jonathan Shook 2021-04-06 16:14:25 -05:00
parent b8dab000e2
commit 65705ff9e2
2 changed files with 47 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

53
sort_docs/eb_metrics_full.puml
View File

@ -1,4 +1,5 @@
@startuml
title: Metrics Types and Scopes in SyncAction
Participant Input as i
Participant Thread as t
@ -43,19 +44,57 @@ group TIMER strides
group HISTOGRAM tries
loop over tries
== for blocking APIs ==
group TIMERS\nexecute\nresult\nresult-success[result-success\nwhen no error]
a -> d: execute
activate d
a <- d: result
deactivate d
end
note right
When the underlying native
driver does not expose an async
API, execute and result must be updated
with the same measurements.
result-success contains the
same measurements as result,
but ONLY for non-exceptional
native driver results.
end note
== for async APIs ==
group TIMER execute
a --> d: execute
a -> d: execute
activate d
a <-- d: future
d -> future **: create
a <- d: future
deactivate d
end
group TIMERS result\n& result-success[result-success\nwhen no error]
a -> d: execute
activate d
a <- d: future
deactivate d
note right
When the underlying native
driver DOES expose an async
API, execute measures
submission of an op to the
native driver, while result
measures the completion
of the op.
result-success contains the
same measurements as result,
but ONLY for non-exceptional
native driver results.
end note
group TIMERS\nresult\nresult-success[result-success\nwhen no error]
a -> future: get
activate future
a <- future: result
deactivate future
end
end