1 / 14

End-to-End performance tuning

End-to-End performance tuning. Brian Davies Gridpp28 Manchester 2012. Areas of Improvements. FTS # Streams # Files Tx Timeout Preparing File Ratio Copy Mechanism G-U-C vs srmcp Asynchronous Ptp Access Method Synchronous vs Asynchronous calls Scheduled vs unscheduled connections.

tavia
Download Presentation

End-to-End performance tuning

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. End-to-End performance tuning Brian Davies Gridpp28 Manchester 2012

  2. Areas of Improvements End-End performance tuning • FTS • # Streams • # Files • Tx Timeout • Preparing File Ratio • Copy Mechanism • G-U-C vs srmcp • Asynchronous Ptp • Access Method • Synchronous vs Asynchronous calls • Scheduled vs unscheduled connections. • Srm-less • Federated xrootd • Costs as well as benefits • TCP/ Window Tuning • Jumbo Frames • Some changes only see benefit in end site also make changes. • WN-WAN tuning • Tcp Window size • ‘Nat’ing • Xrootd configuration/optimisation.

  3. Other areas of optimisation?? • Homogenous network • Mixing WN and Disk Servers can easily reduce network bandwidth • VM components • Splitting services • Databases • Type • Separate node • Internal operation • Cleansing • EG DPM requests DB • DNS Aliasing of multiple machines • Knowledge transfer End-End performance tuning

  4. Who does optimisation and when is the benefit seen. • Some optimisations can be unilateral. • FTS tuning, database improvements etc. • Others have to be co-ordinated • Jumbo Frames • Some optimisation benefits seen straight away. • Others require end host to make changes before benefit is seen. • An “improvement” at one site may degrade another site. • TCP tuning at QMUL/RHUL End-End performance tuning

  5. Differences between T1 and T2s? End-End performance tuning (Some) Current T1 issues will/are problems that a “large” T2 will face in X* years time. Problems a T2 are facing now may have been solved by (a) T1 Y* years ago. A site should/does not need try to re-solve a problem(s) that another site(s)/tier has solved in the past. *(Where X and Y are to be determined).

  6. Manchester Network improvements • Transfers from Manc’ to T1s End-End performance tuning

  7. Manchester network improvements • Reverse direction End-End performance tuning

  8. Manchester Network improvements • Transfers from Manc’ to UK T2s End-End performance tuning

  9. Manchester Network improvements • Transfers from Manc’ to Non UK T2s End-End performance tuning

  10. Manchester Network improvements End-End performance tuning

  11. Effect of streams on RALPPD-T1s • Failing transfers required number of threads per transfer to have to be reduced to 1 per file transfer.` • Deemed more important to receive data from CERN than getting good rate for other sites • Mitigated overall throughput by increasing number of concurrent transfers. • Individual file transfer speed reduced and latency increased. • Once underlining issue re-solved returned to previous settings. End-End performance tuning

  12. Effect of streams on T1s-RALPPD #Streams reduced/Increased Effects transfers TO the site. Effects Some T1s more than others End-End performance tuning

  13. Effect of streams on RALPPD-T1s No (known) changes in streams in reverse direction End-End performance tuning

  14. Other areas of optimisation?? • “In the wiki” • But where? • Which wiki? • ???? End-End performance tuning

More Related