Mercurial > hg > Papers > 2018 > nozomi-master
comparison paper/abstract.tex @ 167:9a072c2d6e12
add English Abstract
| author | Nozomi Teruya <e125769@ie.u-ryukyu.ac.jp> |
|---|---|
| date | Mon, 05 Feb 2018 00:35:52 +0900 |
| parents | 15fed7e1263e |
| children | 707cd7f0689c |
comparison
equal
deleted
inserted
replaced
| 166:d09fb22608f1 | 167:9a072c2d6e12 |
|---|---|
| 18 | 18 |
| 19 | 19 |
| 20 \end{abstract} | 20 \end{abstract} |
| 21 | 21 |
| 22 \begin{abstract_eng} | 22 \begin{abstract_eng} |
| 23 In our laboratory, we propose a method of dividing and describing data as Data Segment and task as Code Segment. | |
| 24 Data segment is a collection of basically data such as integers, character strings and structures. | |
| 25 The Code Segment starts processing in parallel from the time when the input Data Segments are complete and outputs the Data segment of the calculation result. | |
| 26 Using this method, we developed a parallel distributed framework Alice which aims to describe a scalable distributed program with enhanced reliability. | |
| 27 | |
| 28 In Alice, by interposing the process Meta Computation during normal processing, we can change the behavior without changing the code significantly. | |
| 29 Alice can describe a practical distributed application, Meta Computation is confirmed from the example of TreeVNC to make it highly extendable with little specification change. | |
| 30 However, when trying to implement MetaComputation such as NAT traversal, extension is difficult at present and redesign was found to be desirable. | |
| 31 Along with that, I thought that improving counterintuitive API of Alice should guarantee type consistency and improve reliability. | |
| 32 | |
| 33 In this research, we designed the distributed framework Christie based on the findings obtained with Alice. | |
| 34 Christie realizes highly reliable programming with a simple description by using Java Annotation for API. | |
| 35 Also, by enabling multiple Data Gear Managers to be launched, we responded to expansion such as NAT traversal. | |
| 36 | |
| 23 \end{abstract_eng} | 37 \end{abstract_eng} |
| 24 | 38 |