2011 IEEE/IPSJ International Symposium on Applications and the Internet 2011
DOI: 10.1109/saint.2011.45
|View full text |Cite
|
Sign up to set email alerts
|

Reconfigurable TCP: An Architecture for Enhanced Communication Performance in Mobile Cloud Services

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
2
0

Year Published

2012
2012
2016
2016

Publication Types

Select...
1
1

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(2 citation statements)
references
References 6 publications
0
2
0
Order By: Relevance
“…Moreover, overall performance of large-scale distributed data processing is known to degrade when the system contains nodes that have a large communication delay [13]. For loosely coupled communication applications such as mpiBLAST, we can always see a considerable speedup as here what prevails is the computation gained by an increased parallelism over the communication overhead.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…Moreover, overall performance of large-scale distributed data processing is known to degrade when the system contains nodes that have a large communication delay [13]. For loosely coupled communication applications such as mpiBLAST, we can always see a considerable speedup as here what prevails is the computation gained by an increased parallelism over the communication overhead.…”
Section: Introductionmentioning
confidence: 99%
“…(1) begin (2) Data: (the set of tasks); (3) (communication graph); (4) (the set of processors); (5) (the background load of processors); (6) Result: M: → ; // A task mapping (7) nObjs ← NumObjs; // number of migratable objects (8) ObjectHeap objHeap(nObjs + 1); // declare a object heap objHeap (9) → maxhAllObjs; // max for all migratable objects (10) ProcessorHeap lightProcessors(P); // declare a processor heap lightProcessors (11) → lightProcessors; (12) for ← 1 to nObjs do (13) minLoad ← MAX DOUBLE; // Initially the minimum load minLoad are set to MAX DOUBLE (14) o ← objHeap.deleteMax(); // Find the object o with high loads (15) cpuDonor ← lightProcessors->deleteMin(); // Find the migratable target (processor) with light loads (16) ← ∑ ∈ ∧ ( )= ( ∧ ); // comm cost represents communication cost (17) newLoad ← cpuDonor.load + comm cost; // Recalculate new load considering communication cost (18) if newload < minLoad then (19) minLoad ← newLoad; (20) newDonor ← cpuDonor; // Find new migratable processor (21) end if (22) for cpuDonor ∈ comm do (23) ← ∑ ∈ ∧ ( )= ( ∧ ); (24) newLoad ← cpuDonor.load + comm cost; (25) if newLoad < minLoad then (26) minLoad ← newLoad; (27) newDonor ← cpuDonor; // newDonor: new migratable processor (28) end if (29) end (3) Overhead Calculation. The overhead of each leaf node can be represented as…”
mentioning
confidence: 99%