Experience with Using a Performance Predictor During使用性能预测的经验.pptxVIP

Experience with Using a Performance Predictor During Developmenta Distributed Storage System Tale Lauro Beltr?o Costa*, Jo?o Brunet+, Lile Hattori#, Matei Ripeanu* * NetSysLab/ECE, UBC (University of British Columbia) + DSC, UFCG (Federal University of Campina Grande) # Microsoft Corp. How it is (typically) done? Profilers to monitor behaviour They pinpoint code regions that take too long ? will receive attention 2 Developers decide when they have reached “good-enough” efficiency High performance must be reached while keeping resource cost low An Example ? More Storage Nodes More Application Nodes ? 3 Cluster size: 20 Nodes Target performance is not obvious Wide performance variation among configurations. Application Time (seconds in log scale) Experience with using a performance predictor during the software development process What are the limitations and challenges of using a performance predictor as part of the development process? 4 Context: A Distributed Storage System MosaStore, a distributed storage system A manager, several clients, several storage servers Approximately 11,000 lines of code, Around 15 developers involved over time 5 Code papers at: MosaStore.net Sources of complexity Multiple interacting components with complex interactions Complex data and control paths Contention (network, component level) Variability in the environment Deployment choices (configuration, provisioning ) 6 Performance Predictor Performance Predictor 7 Supporting Storage configuration for I/O Intensive Workflows, L. B. Costa, S. Al-Kiswany, H. Yang, M. Ripeanu, ICS,’14 Energy Prediction for I/O Intensive Workflow Applications, H. Yang, L. B. Costa, M. Ripeanu, MTAGS’14 Development Flow 8 Performance Anomalies Case 1: Lack of Randomness Case 2: Lock Overhead Case 3: Connection Timeout 9 Case 3: Connection Timeout Benchmark Time (seconds) Actual vs. Expected 10 Actual vs. Predicted: Large Mismatch Case 3: Connection Timeout Context