2014
DOI: 10.1007/s10922-014-9331-7
|View full text |Cite
|
Sign up to set email alerts
|

Online Incremental Clock Synchronization

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

2014
2014
2021
2021

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(5 citation statements)
references
References 27 publications
0
5
0
Order By: Relevance
“…The absence of a global clock analysis in a distributed system is challenging and may even cause messages to seemingly be received before being issued (message inversion). The convex hull algorithm was proposed by Jabbarifar et al [24] to solve this problem. The idea is to use event matching between different hosts to unify the clock sources.…”
Section: Kernel Modulesmentioning
confidence: 99%
See 1 more Smart Citation
“…The absence of a global clock analysis in a distributed system is challenging and may even cause messages to seemingly be received before being issued (message inversion). The convex hull algorithm was proposed by Jabbarifar et al [24] to solve this problem. The idea is to use event matching between different hosts to unify the clock sources.…”
Section: Kernel Modulesmentioning
confidence: 99%
“…In this case, the causality between events is the only way to get a partial ordering, which is enough for the analysis. The fully incremental convex hull synchronization algorithm [24] is used to solve the problem of trace synchronization in distributed systems. The algorithm is based on matching an event a from one trace and an event b from the other.…”
Section: Multilevelmentioning
confidence: 99%
“…In this case, the causality between events can be used F I G U R E 3 Client and OSD analysis before and after clock synchronization [Colour figure can be viewed at wileyonlinelibrary.com] to get partial ordering, which is sufficient to have meaningful trace data. In this article, we used the fully incremental convex hull algorithm 32 to synchronize the traces. The algorithm is based on the causality between the events of the different traces.…”
Section: Trace Correlationmentioning
confidence: 99%
“…We use the fully incremental convex hull synchronization algorithm to achieve offline trace synchronization, introduced by [18] for distributed traces synchronization. Each guest trace is processed individually and synchronized according to the host's trace whose timeline is taken as a reference.…”
Section: Event Matchingmentioning
confidence: 99%