INTRODUCTION :
In operating systems, invoking a system service is usually a heavy-weight operation due to protection domain crossing. In distributed systems, invoking remote services is more expensive than invoking local services due to network latency and processing overhead.
The COMPOSITECALL design pattern enables the extension of server interfaces for safe execution of repeated sequences of service calls and simple control structures. The pattern is also known as BATCHING [1]. It provides the means to compose separate calls to a server into a single one. A COMPOSITECALL is indeed a program a client sends for execution in the server domain. INTRODUCTION
MAIN PARTICIPANT IN COMPOSITE CALL :
MAIN PARTICIPANT IN COMPOSITE CALL
COMPOSITE CALL PATERN :
COMPOSITE CALL PATERN
COMPOSITE CALL INSTANCES FOR LINUX SYSTEM CALLS :
COMPOSITE CALL INSTANCES FOR LINUX SYSTEM CALLS
NORMAL SYSTEM CALL PATH :
NORMAL SYSTEM CALL PATH
COMPOSITE CALL BASED COPY vs TRADIONAL COPY ON LINUX :
COMPOSITE CALL BASED COPY vs TRADIONAL COPY ON LINUX
COMPOSITE CALL BASED COPY vs NFS BASED COPY :
COMPOSITE CALL BASED COPY vs NFS BASED COPY
CONCLUSION :
Experimental results show that, although the COMPOSITECALL mechanism can provide great performance improvements, its use must be carefully analyzed. In some cases, the overhead it imposes may be larger than the performance gain it provides. We plan to perform further experiments on distributed services where we expect to obtain very significant speedups. CONCLUSION
THANK YOU :
THANK YOU