1 / 38

Centralized Coordinator

Centralized Coordinator. Outline. Query type 1, 2, 3 Setup 1, 2, 3 Intra WSs Parallelism vs. No WSs Parallelism Analyze results Conclusions. ∏. GC. YP. Branch. Join. YP. BR. . Project. GC. . ∏. TL. Query type. Query type 1 Query type 2. ∏. GC. YP. BR. . . TL1. ∏.

hisano
Download Presentation

Centralized Coordinator

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Centralized Coordinator

  2. Outline • Query type 1, 2, 3 • Setup 1, 2, 3 • Intra WSs Parallelism vs. No WSs Parallelism • Analyze results • Conclusions

  3. ∏ GC YP Branch Join YP BR  Project GC  ∏ TL Query type • Query type 1 • Query type 2

  4. ∏ GC YP BR   TL1 ∏ Split TL2 Union TL52 Query type • Query type 3

  5. Setup1 Centralized Coordinator Web Service (CC WS) Yellow Pages Web Service (YP WS) Broker WS SQL-Server (YP) Work Load Generator (WLG) Geocoder Web Service (GC WS) SQL-Server (GC) Tigerline Web Service (TL WS) SQL-Server (TL)

  6. Setup2 Broker WS Work Load Generator (WLG) Yellow Pages Web Service (YP WS) Geocoder Web Service (GC WS) Tigerline Web Service (TL WS) Centralized Coordinator Web Service (CC WS)

  7. Setup3 YP WS YP WS YP WS GC WS GC WS GC WS TL WS TL WS TL WS CC WS CC WS CC WS Gateway12 Gateway1 Gateway2 12 Gateways Broker WS WLG

  8. Centralized Coordinator YP WS YP WS YP WS GC WS GC WS GC WS TL WS TL WS TL WS CC WS CC WS CC WS Gateway12 Gateway1 Gateway2 Broker WS Show all automotive tire businesses in my zip-code WLG

  9. Centralized Coordinator YP WS YP WS YP WS GC WS GC WS GC WS TL WS TL WS TL WS CC WS CC WS CC WS Gateway12 Gateway1 Gateway2 Broker WS Request a copy of CC WS WLG

  10. Centralized Coordinator YP WS YP WS YP WS GC WS GC WS GC WS TL WS TL WS TL WS CC WS CC WS CC WS Gateway12 Gateway12 Gateway1 Gateway2 Broker WS http://Gateway12/CCWS WLG

  11. Centralized Coordinator YP WS YP WS YP WS GC WS GC WS GC WS TL WS TL WS TL WS CC WS CC WS CC WS Gateway12 Gateway12 Gateway1 Gateway2 Query (zip code, business category, subcategory) Broker WS WLG

  12. Centralized Coordinator YP WS YP WS YP WS GC WS GC WS GC WS TL WS TL WS TL WS CC WS CC WS CC WS Gateway12 Gateway1 Gateway2 request a copy of YP WS Broker WS WLG

  13. Centralized Coordinator YP WS YP WS YP WS GC WS GC WS GC WS TL WS TL WS TL WS CC WS CC WS CC WS Gateway12 Gateway12 Gateway1 Gateway2 http://Gateway2/YPWS Broker WS WLG

  14. Centralized Coordinator YP WS YP WS YP WS Query (zip code, business category, subcategory) GC WS GC WS GC WS TL WS TL WS TL WS CC WS CC WS CC WS Gateway12 Gateway12 Gateway1 Gateway2 Broker WS WLG

  15. Centralized Coordinator YP WS YP WS YP WS Address, name, etc for each business GC WS GC WS GC WS TL WS TL WS TL WS CC WS CC WS CC WS Gateway12 Gateway12 Gateway1 Gateway2 Broker WS WLG

  16. Centralized Coordinator YP WS YP WS YP WS GC WS GC WS GC WS TL WS TL WS TL WS GCThread CC WS CC WS CC WS Gateway1 Gateway2 TL Thread request a copy of GC WS Broker WS request a copy of TL WS WLG

  17. Centralized Coordinator YP WS YP WS YP WS GC WS GC WS GC WS TL WS TL WS TL WS GC Thread CC WS CC WS CC WS Gateway12 Gateway1 Gateway2 TL Thread http://Gateways2/GCWS Broker WS http://Gateway1/TLWS WLG

  18. Centralized Coordinator No WSs Parallelism YP WS YP WS YP WS GC WS GC WS GC Thread GC WS TL WS TL WS TL WS CC WS CC WS CC WS Query (address) Gateway1 TL Thread Gateway12 Gateway12 Gateway12 Gateway2 Query (address) Broker WS WLG

  19. Centralized Coordinator No WSs Parallelism YP WS YP WS YP WS GC WS GC WS GC Thread GC WS TL WS TL WS TL WS CC WS CC WS Results CC WS TL Thread Gateway12 Gateway12 Gateway12 Gateway1 Gateway2 Results Broker WS WLG

  20. Centralized Coordinator Intra WSs Parallelism YP WS YP WS YP WS GC WS GC WS GC WS TL WS TL WS TL WS CC WS CC WS CC WS Query (address) Gateway1 Gateway2 Gateway11 Query (address) 1 2 YP WS GC WS Query (address) GC Thread TL WS CC WS n Broker WS Gateway12 WLG

  21. Centralized Coordinator Intra WSs Parallelism YP WS YP WS YP WS GC WS GC WS GC WS TL WS TL WS TL WS CC WS CC WS CC WS Results (latitude, longitude) Gateway1 Gateway2 Gateway11 Results (latitude, longitude) 1 2 YP WS GC WS Results (latitude, longitude) GC Thread TL WS CC WS n Broker WS Gateway12 WLG

  22. Centralized Coordinator Intra WSs Parallelism YP WS YP WS YP WS GC WS GC WS GC WS TL WS TL WS TL WS CC WS CC WS CC WS Gateway1 Gateway2 Gateway11 1 2 YP WS GC WS GC Thread TL WS CC WS n Broker WS Gateway12 WLG

  23. Centralized Coordinator YP WS YP WS YP WS GC WS GC WS GC WS TL WS TL WS TL WS CC WS CC WS CC WS Gateway12 Gateway1 Gateway2 All results from YP, GC, TL Broker WS WLG

  24. Centralized Coordinator YP WS YP WS YP WS GC WS GC WS GC WS TL WS TL WS TL WS CC WS CC WS CC WS Gateway12 Gateway1 Gateway2 Broker WS WLG Show results

  25. Query Type by Query Type No WSs Parallelism • Setup 1: • query type 1 <= query type 2 <= query type 3 • Setup 2: • query type 1 < query type 2 <=> query type 3 • Setup 3: • query type 1 <= query type 2 < query type 3 • Querying with zip code doesn’t utilize multi-threading in query type 3

  26. Setup 1: query type 1 <= query type 2 <= query type 3 Zip code • Values are execution time (ET) • ET is median • ET is in milliseconds • # of outputs (80303) = 2 • # of outputs (30032) = 16

  27. Setup 2: query type 1 < query type 2 <=> query type 3 Zip code • Values are execution time (ET) • ET is median • ET is in milliseconds • # of outputs (80303) = 2 • # of outputs (30032) = 16

  28. Setup 3: query type 1 <= query type 2 < query type 3 Zip code • Values are execution time (ET) • ET is median • ET is in milliseconds • # of outputs (80303) = 2 • # of outputs (30032) = 16

  29. Setup by Setup No WSs Parallelism • Query Type 1: • setup 1 => setup 2 <= setup 3 • Query Type 2: • setup 1 <= setup 2 <=> setup 3 • Query Type 3: • setup 1 <= setup 2 < setup 3 • setup1 which has only one service in one node gives better ETs

  30. Query Type 1: setup 1 => setup 2 <= setup 3 Zip code • Values are execution time (ET) • ET is median • ET is in milliseconds • # of outputs (80303) = 2 • # of outputs (30032) = 16

  31. Query Type 2: setup 1 <= setup 2 <=> setup 3 Zip code • Values are execution time (ET) • ET is median • ET is in milliseconds • # of outputs (80303) = 2 • # of outputs (30032) = 16

  32. Query Type 3: setup 1 <= setup 2 < setup 3 Zip code • Values are execution time (ET) • ET is median • ET is in milliseconds • # of outputs (80303) = 2 • # of outputs (30032) = 16

  33. Intra WSs Parallelism vs. No WSs Parallelism • Only setup3 • Query Type 1: • Intra WSs Parallelism (IWP) < No WSs Parallelism (NWP) • GC ET with NWP < GC ET with IWP. • Query Type 2: • NWP < IWP • Query Type 3: • NWP < IWP • SQL Server overloading due to multi-threading causes high GC & TL ETs

  34. Query Type 1: IWP < NWP Zip code • Values are execution time (ET) • ET is median • ET is in milliseconds • # of outputs (80303) = 2 • # of outputs (30032) = 16

  35. Query Type 1: GC ET with NWP < GC ET with IWP Zip code • Values are execution time (ET) • ET is median • ET is in milliseconds • # of outputs (80303) = 2 • # of outputs (30032) = 16

  36. Query Type 2: NWP < IWP Zip code • Values are execution time (ET) • ET is median • ET is in milliseconds • # of outputs (80303) = 2 • # of outputs (30032) = 16

  37. Query Type 3: NWP < IWP Zip code • Values are execution time (ET) • ET is median • ET is in milliseconds • # of outputs (80303) = 2 • # of outputs (30032) = 16

  38. Conclusions • Setup 1 which one node has only one service has better Execution Time • Intra WSs Parallelism causes SQL Sever overloading • SQL Server overloading increases CC Execution Time • Need better broker which can avoid SQL Server overloading

More Related