Performance Evaluation Workshop ISCC'09

411 views

Published on

Published in: Technology, Travel
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
411
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Performance Evaluation Workshop ISCC'09

  1. 1. Experiments and Performance Evaluation of Event Driven Mashups Sousse July, 5th 2009 Michele Stecca [email_address] CIPI – University of Padova and Genova (Italy)
  2. 2. Outline <ul><li>The OPUCE project </li></ul><ul><li>Mashup definition </li></ul><ul><li>Description of the Mashup execution architectures </li></ul><ul><li>Performance tests </li></ul><ul><ul><li>Test setup </li></ul></ul><ul><ul><li>Results </li></ul></ul><ul><ul><li>Conclusions </li></ul></ul>
  3. 3. The OPUCE project <ul><li>O pen P latform for U ser-centric service C reation and E xecution (FP6 IP Nov. ‘06 – Apr ‘09) </li></ul><ul><li>User Generated Services </li></ul><ul><li>Main components of the platform </li></ul><ul><ul><li>Service Creation Environment (SCE) </li></ul></ul><ul><ul><li>Service Lifecycle Manager (SLM) </li></ul></ul><ul><ul><li>Service Execution Environment (SEE) </li></ul></ul><ul><ul><li>Portal </li></ul></ul>
  4. 4. Event Driven Mashup Definition <ul><li>Base Services (Basic blocks) </li></ul><ul><li>Service Compositions (Mashups) </li></ul><ul><li>Web Service communications between Base Services </li></ul>4 Different SEE Implementations
  5. 5. BPEL-based solution <ul><li>Mashup execution based on a BPEL engine </li></ul><ul><li>BPEL is not suitable for event driven applications </li></ul><ul><li>Definition of a “standard” BPEL script structure </li></ul>BSs Container Orchestrator on BPEL Engine BS_1 BS_n BSs Container BS_1 BS_n
  6. 6. JSLEE-based solution <ul><li>Sessions, scalability and asynchronous event management provided by the Mobicents JSLEE Container </li></ul>JSLEE stands for JAIN Service Logic Execution Environment BSs Container Orchestrator on JSLEE container BS_1 BS_n BSs Container BS_1 BS_n
  7. 7. Plain JAVA solution <ul><li>Stateless Orchestration </li></ul><ul><li>Ad-hoc Orchestrator lighter than BPEL engine: only event routing </li></ul><ul><li>Scalability thanks to Orchestrator replication </li></ul>Orchestrator Management System BSs Container Orchestrator (O_Id=1) BS_1 BS_n BSs Container BS_1 BS_n Orchestrator (O_Id=m)
  8. 8. Fully Distributed Solution <ul><li>Stateless Orchestration </li></ul><ul><li>No centralized Orchestrator: intrinsic scalability </li></ul>SEE1.1: fully distributed solution BaseService BaseService BaseService BaseService BaseService Orchestration Proxy BS SC BS SC BS SC BS SC BS SC BS SC = Base Service superclass OPUCE Service Trigger or OPUCE Portal 1. notifyEvent [starting a session] 2. first base service is invoked with event 3. only error and final events are routed back to the OrchestrationProxy Distributed execution network
  9. 9. Test Setup <ul><li>Traffic generated by SoapUI at different rates (50 – 100 – 200 reqs/sec) </li></ul><ul><li>Important: BPEL-based solution crashes as soon as the traffic rate goes beyond 10 reqs/sec </li></ul>traffic generator orchestrator bs „SleepA“ Software test setup Start SleepA SleepB SleepA SleepB SleepA End bs „SleepB“ SleepB SleepA SleepA SleepB T1 T2 Hardware test setup
  10. 10. Test Results & Conclusions <ul><li>Which one? </li></ul><ul><ul><li>BPEL-solution is not suitable for event driven applications </li></ul></ul><ul><ul><li>The specific implementation of the JSLEE standard should be improved </li></ul></ul><ul><ul><li>The Plain JAVA solution shows good performance and complete control </li></ul></ul><ul><ul><li>The fully distributed solution is better when high performance is required </li></ul></ul>166 5,20 91,03 5,11 48,44 3,34 Distributed 51,85 226,12 53,21 173,91 48,15 9,53 JSLEE 161 8,08 91,06 5,87 48,58 5,70 Plain JAVA T(reqs/sec) L(ms) T(reqs/sec) L(ms) T(reqs/sec) L(ms) Config_3 (200 reqs/sec) Config_2 (100 reqs/sec) Config_1 (50 reqs/sec)
  11. 11. Questions & Answers Thank you!

×