Proceedings of 20th International Computer Software and Applications Conference: COMPSAC '96
DOI: 10.1109/cmpsac.1996.542427
|View full text |Cite
|
Sign up to set email alerts
|

A popularity-based data allocation scheme for a VOD server

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Publication Types

Select...
2
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(3 citation statements)
references
References 4 publications
0
3
0
Order By: Relevance
“…In other words, if data unit i is being retrieved, then its successive unit (i + 1) will be accessed next. Compared to traditional computing, data retrieval for on-demand services is more predictable [5]. Therefore, a careful data placement scheme will improve the spatial locality of data retrieval.…”
Section: Data Localitymentioning
confidence: 98%
“…In other words, if data unit i is being retrieved, then its successive unit (i + 1) will be accessed next. Compared to traditional computing, data retrieval for on-demand services is more predictable [5]. Therefore, a careful data placement scheme will improve the spatial locality of data retrieval.…”
Section: Data Localitymentioning
confidence: 98%
“…The load balancing issue stems from different object popularities among the movie library, which is a nontrivial issue when modeling and designing large-scale multimedia servers. Because some media objects are more popular than others, the retrieval of media objects is highly skewed in many multimedia applications such as video-on-demand [16][41][57] [62]. A multimedia server with large amount of video objects has to take video popularity into account.…”
Section: Load Balancingmentioning
confidence: 99%
“…It maintains a root directory in the form of a B + -tree. Each entry in the root directory points to a [16], [24] Interleave Separate Analyze [4], [6] Simulate [35], [39] Sync Cluster Same Analyze [29] Implement [43] Async Cluster Same Simulate [36], [10], [11], [3] Implement [17], [18], [9] Interleave subdirectory that records the physical block locations of an object. The subdirectory is also implemented as a B + -tree.…”
Section: Directory Managermentioning
confidence: 99%