2007
DOI: 10.1002/cpe.1152
|View full text |Cite
|
Sign up to set email alerts
|

An analytical study on optimizing the lookup performance of distributed hash table systems under churn

Abstract: SUMMARYThe phenomenon of system churn degrades the lookup performance of distributed hash table (DHT) systems greatly. To handle the churn, a number of approaches have been proposed to date. However, there is a lack of theoretical analysis to direct how to make design choices under different churn rates and how to configure their parameters optimally. In this paper, we analytically study three important aspects on optimizing DHT lookup performance under churn, i.e. lookup strategy, lookup parallelism and looku… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
12
0

Year Published

2008
2008
2020
2020

Publication Types

Select...
3
3

Relationship

0
6

Authors

Journals

citations
Cited by 10 publications
(12 citation statements)
references
References 21 publications
0
12
0
Order By: Relevance
“…From the figure it can also be seen that initial network size has a more pronounced effect on the expected object lifetime, when no repair is used than when repair is used. Wu, Tian and Ng that assumes object repair [123]. For this figure, a repair rate of µ = 1/180 and a required number of replicas of R = 10 were used.…”
Section: Model Resultsmentioning
confidence: 99%
See 3 more Smart Citations
“…From the figure it can also be seen that initial network size has a more pronounced effect on the expected object lifetime, when no repair is used than when repair is used. Wu, Tian and Ng that assumes object repair [123]. For this figure, a repair rate of µ = 1/180 and a required number of replicas of R = 10 were used.…”
Section: Model Resultsmentioning
confidence: 99%
“…This chapter mainly extends and improves upon the work by Wu, Tian and Ng [123]. The related work models three characteristics of distributed hash table (DHT) lookups under churn: expected lookup latency of various routing schemes, expected lookup overhead of various routing schemes and expected object lifetime.…”
Section: Background and Related Workmentioning
confidence: 89%
See 2 more Smart Citations
“…Therefore, once the originator gets the expected result from one process, it can terminate another lookup process and avoid the remaining unnecessary costs for the overlay. Furthermore, iterative routing is robust to the high churn circumstance [7]. If there is no response after a timeout no less than the average round-trip time (RTT), the originator knows which hop failed to respond and will initiate a retry immediately.…”
Section: Lookup Algorithmmentioning
confidence: 99%