1 / 20

An analysis of data transfer issues From GRIF‐LAL and IN2P3‐LPC to TOKYO

An analysis of data transfer issues From GRIF‐LAL and IN2P3‐LPC to TOKYO. Tomoaki Nakamura ICEPP , University of TOKYO. Data transfer matrix in FR -cloud. from Feb. 2012 to Jun. 2012. Problems in transfers from GRIF-LAL and IN2P3-LPC to TOKYO.

cirila
Download Presentation

An analysis of data transfer issues From GRIF‐LAL and IN2P3‐LPC to TOKYO

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. An analysis of data transfer issuesFrom GRIF‐LAL and IN2P3‐LPC to TOKYO Tomoaki Nakamura ICEPP, University of TOKYO Tomoaki Nakamura ICEPP, Univ. of Tokyo

  2. Data transfer matrix in FR-cloud from Feb. 2012 to Jun. 2012 Problems in transfers from GRIF-LAL and IN2P3-LPC to TOKYO. Timeout occurs occasionally for files bigger than 1 GB. Such hotspots affect smooth data distribution in FR-cloud, since DDM assumes uniform connectivity in a cloud. This problems have already indicated in, https://savannah.cern.ch/bugs/?90998 GRIF-LAL → TOKYO IN2P3-LCP → TOKYO Tomoaki Nakamura ICEPP, Univ. of Tokyo

  3. Transfer from GRIF-LAL to TOKYO (file size: 1GB) , reference LYON http://www.icepp.jp/monitor/transferspeed/ Data are collected by daily test transfer (file size is 1GB) between storages using the “lcg-rep” with 10 streams. Plots are shown since Dec. 2011. For the transfer from GRIF-LAL to TOKYO, almost of data points indicate very slow rate except for some points. For the transfer from TOKYO to GRIF-LAL, basically no problem even as compared to LYON. Transfer from TOKYO to GRIF-LAL (file size: 1GB) , reference LYON Tomoaki Nakamura ICEPP, Univ. of Tokyo

  4. Transfer from IN2P3-LPC to TOKYO (file size: 1GB) reference LYON Data are collected by same way with GRIF-LAL. For the transfer from IN2P3-LPC to TOKYO, the transfer rate is not always so bad and much better than the case of GRIF-LAL. However, it is very unstable basically. For the transfer from TOKYO to IN2P3-LPC, it seems no problem similar to the case for the transfer from TOKYO to GRIF-LAL. Transfer from TOKYO to IN2P3-LPC (file size: 1GB)reference LYON Tomoaki Nakamura ICEPP, Univ. of Tokyo

  5. Transfer from GRIF-LAL to TOKYO (file size: 50MB) ~ Dec. 20, 2011 ← no data → Then, go to check older data since Sep. 2011. These plots are made by using transfer of small files (50MB). It should be insensitive to TCP fair share parameters. For the transfer from GRIF-LAL to TOKYO, obviously the rate drop down suddenly around Dec.20, 2011. For the transfer from IN2P3-LPC to TOKYO, there are no significant changes before and after the Dec. 20, 2011. ← no data → Transfer from IN2P3-LPC to TOKYO (file size: 50MB) Tomoaki Nakamura ICEPP, Univ. of Tokyo

  6. perfSONAR at TOKYO (TOKYO : GRIF-LAL) http://perfsonar2.icepp.jp/serviceTest/index.cgi?eventType=bwctl As far as take a look at the perfSONAR throughput initiated by an instance at TOKYO, network itself seems to have no problem between GRIF-LAL and TOKYO. Unfortunately, there are no data by perfSONAR for IN2P3-LPC. Tomoaki Nakamura ICEPP, Univ. of Tokyo

  7. Transfer from IN2P3-LPC to TOKYO sorted by FSs in IN2P3-LPC since Dec. 2011 file size: 1GB ● all data points □ average with standard error ID Num. transferred File server 1 8 clrdata-dpm11.in2p3.fr 2 11 clrdata-dpm12.in2p3.fr 3 12 clrdata-dpm13.in2p3.fr 4 7 clrdata-dpm14.in2p3.fr 5 14 clrdata-dpm15.in2p3.fr 6 11 clrdata-dpm16.in2p3.fr 7 35 clrdata-dpm21.in2p3.fr 8 35 clrdata-dpm22.in2p3.fr 9 32 clrdata-dpm25.in2p3.fr 10 8 clrdata-dpm26.in2p3.fr 11 4 clrdata-dpm27.in2p3.fr 12 7 clrdata-dpm28.in2p3.fr 13 5 clrgpfs2srv-dpm02.in2p3.fr 14 3 clrgpfs2srv-dpm03.in2p3.fr 15 7 clrgpfs2srv-dpm04.in2p3.fr 16 6 clrgpfs2srv-dpm05.in2p3.fr 17 1 clrgpfs2srv-dpm06.in2p3.fr Then, go to check file server dependence. Average transfer rate indicate some file server dependence. Need to contact with site admin. of IN2P3-LPC, and check any differences on some parameters in file servers. Tomoaki Nakamura ICEPP, Univ. of Tokyo

  8. Transfer from IN2P3-LPC to TOKYO sorted by FSs in TOKYO since Dec. 2011 file size: 1GB ● all data points □ average with standard error ID Num. transferred File server 1 13 lcg-fs01.icepp.jp 2 17 lcg-fs02.icepp.jp 3 11 lcg-fs03.icepp.jp 4 17 lcg-fs04.icepp.jp 5 11 lcg-fs05.icepp.jp 6 13 lcg-fs06.icepp.jp 7 13 lcg-fs07.icepp.jp 812lcg-fs08.icepp.jp 912lcg-fs09.icepp.jp 1010lcg-fs10.icepp.jp 1115lcg-fs11.icepp.jp 1214lcg-fs12.icepp.jp 1311lcg-fs13.icepp.jp 147lcg-fs14.icepp.jp 1511lcg-fs15.icepp.jp 167lcg-fs16.icepp.jp 1712 lcg-fs17.icepp.jp Since TOKYO is just a receiver of file transfer in this case, there is no file server dependence as expected.

  9. Transfer from GRIF-LAL to TOKYO sorted by FSs in GRIF-LAL since Dec. 2011 file size: 1GB ● all data points □ average with standard error ID Num. transferred File server 1 22 grid18.lal.in2p3.fr 2 5 grid20.lal.in2p3.fr 3 1 grid21.lal.in2p3.fr 4 18 grid23.lal.in2p3.fr 5 14 grid24.lal.in2p3.fr 6 30 grid27.lal.in2p3.fr 7 2 grid28.lal.in2p3.fr 8 21 grid29.lal.in2p3.fr 9 25 grid37.lal.in2p3.fr 10 27 grid38.lal.in2p3.fr 11 17 grid39.lal.in2p3.fr 12 15 grid41.lal.in2p3.fr Average transfer rate is too bad except for two file servers. According to the site admin. of GRIF-LAL, No. 9 and No. 12 are relatively new file servers. However, there are no differences of settings for data transfer in all file servers… † † Tomoaki Nakamura ICEPP, Univ. of Tokyo

  10. Transfer from GRIF-LAL to TOKYO sorted by FSs in TOKYO since Dec. 2011 file size: 1GB ● all data points □ average with standard error ID Num. transferred File server 1 17 lcg-fs01.icepp.jp 2 6 lcg-fs02.icepp.jp 3 9 lcg-fs03.icepp.jp 4 15 lcg-fs04.icepp.jp 5 15 lcg-fs05.icepp.jp 6 11 lcg-fs06.icepp.jp 7 9 lcg-fs07.icepp.jp 813lcg-fs08.icepp.jp 911lcg-fs09.icepp.jp 108lcg-fs10.icepp.jp 1118lcg-fs11.icepp.jp 1212lcg-fs12.icepp.jp 1311lcg-fs13.icepp.jp 1416lcg-fs14.icepp.jp 1513lcg-fs15.icepp.jp 168lcg-fs16.icepp.jp 175lcg-fs17.icepp.jp There is no file server dependence in TOKYO same as for IN2P3-LPC case. Tomoaki Nakamura ICEPP, Univ. of Tokyo

  11. Transfer from GRIF-LAL to TOKYO sorted by FSs in GRIF-LAL Sep.1, 2011 – Dec. 19, 2011 file size: 50MB ● all data points □ average with standard error ID Num. transferred File server 1 19 grid18.lal.in2p3.fr 2 0 grid20.lal.in2p3.fr 3 1 grid21.lal.in2p3.fr 4 11 grid23.lal.in2p3.fr 5 4 grid24.lal.in2p3.fr 6 15 grid27.lal.in2p3.fr 7 3 grid28.lal.in2p3.fr 8 17 grid29.lal.in2p3.fr 9 21 grid37.lal.in2p3.fr 10 20 grid38.lal.in2p3.fr 11 16 grid39.lal.in2p3.fr 12 0 grid41.lal.in2p3.fr Indeed, there was no file server dependence for the transfer from GRIF-LAL to TOKYO before Dec. 20, 2011. The transfer rate was also not so bad even for the 50MB file transferring. Tomoaki Nakamura ICEPP, Univ. of Tokyo

  12. Transfer from GRIF-LAL to TOKYO sorted by FSs in GRIF-LAL Dec.20, 2011 – Jul. 1, 2012 file size: 50MB ● all data points □ average with standard error ID Num. transferred File server 1 20 grid18.lal.in2p3.fr 2 4 grid20.lal.in2p3.fr 3 1 grid21.lal.in2p3.fr 4 17 grid23.lal.in2p3.fr 5 11 grid24.lal.in2p3.fr 6 25 grid27.lal.in2p3.fr 7 2 grid28.lal.in2p3.fr 8 17 grid29.lal.in2p3.fr 9 24 grid37.lal.in2p3.fr 10 24 grid38.lal.in2p3.fr 11 14 grid39.lal.in2p3.fr 12 15 grid41.lal.in2p3.fr However, the average rate was dropped down after Dec. 20 independent of difference of file servers(see previous page). Tomoaki Nakamura ICEPP, Univ. of Tokyo

  13. All Sites, 7days average (2011-09-01 ~ 2012-07-01) AGLT2_DATADISK AUSTRALIA-ATLAS_DATADISK BEIJING-LCG2_DATADISK BNL-OSG2_DATADISK CA-ALBERTA-WESTGRID-T2_DATADISK CA-MCGILL-CLUMEQ-T2_DATADISK CA-SCINET-T2_DATADISK CA-VICTORIA-WESTGRID-T2_DATADISK CERN-PROD_DATADISK CSCS-LCG2_DATADISK CSTCDIE_DATADISK CYFRONET-LCG2_DATADISK DESY-HH_DATADISK DESY-ZN_DATADISK FZK-LCG2_DATADISK GOEGRID_DATADISK GRIF-IRFU_DATADISK GRIF-LPNHE_DATADISK HEPHY-UIBK_DATADISK IFAE_DATADISK IFIC-LCG2_DATADISK ILLINOISHEP_DATADISK IL-TAU-HEP_DATADISK IN2P3-CC_DATADISK IN2P3-CPPM_DATADISK IN2P3-LAPP_DATADISK IN2P3-LPC_DATADISK IN2P3-LPSC_DATADISK INFN-FRASCATI_DATADISK INFN-MILANO-ATLASC_DATADISK INFN-NAPOLI-ATLAS_DATADISK INFN-ROMA1_DATADISK INFN-T1_DATADISK ITEP_DATADISK JINR-LCG2_DATADISK LIP-COIMBRA_DATADISK LIP-LISBON_DATADISK LRZ-LMU_DATADISK MPPMU_DATADISK MWT2_DATADISK NCG-INGRID-PT_DATADISK NDGF-T1_DATADISK NET2_DATADISK NIKHEF-ELPROD_DATADISK OU_OCHEP_SWT2_DATADISK PIC_DATADISK PRAGUELCG2_DATADISK RAL-LCG2_DATADISK RO-02-NIPNE_DATADISK RO-07-NIPNE_DATADISK RO-14-ITIM_DATADISK RO-16-UAIC_DATADISK RRC-KI_DATADISK RU-MOSCOW-FIAN-LCG2_DATADISK RU-MOSCOW-SINP-LCG2_DATADISK RU-PNPI_DATADISK RU-PROTVINO-IHEP_DATADISK SARA-MATRIX_DATADISK SE-SNIC-T2_DATADISK SFU-LCG2_DATADISK SLACXRD_DATADISK SWT2_CPB_DATADISK TAIWAN-LCG2_DATADISK TECHNION-HEP_DATADISK TOKYO-LCG2_DATADISK TR-10-ULAKBIM_DATADISK TRIUMF-LCG2_DATADISK UAM-LCG2_DATADISK UKI-LT2-QMUL_DATADISK UKI-LT2-RHUL_DATADISK UKI-LT2-UCL-HEP_DATADISK UKI-NORTHGRID-LANCS-HEP_DATADISK UKI-NORTHGRID-LIV-HEP_DATADISK UKI-NORTHGRID-MAN-HEP_DATADISK UKI-NORTHGRID-SHEF-HEP_DATADISK UKI-SCOTGRID-ECDF_DATADISK UKI-SCOTGRID-GLASGOW_DATADISK UKI-SOUTHGRID-BHAM-HEP_DATADISK UKI-SOUTHGRID-CAM-HEP_DATADISK UKI-SOUTHGRID-OX-HEP_DATADISK UKI-SOUTHGRID-RALPP_DATADISK UNI-FREIBURG_DATADISK WEIZMANN-LCG2_DATADISK WUPPERTALPROD_DATADISK small: 0 ~ 100MB Comparison with the other sites. Data transfer throughput for the transfer from GRIF-LALare extracted from ATLAS dashboad. Red points are the average for each time bin. Apparently, you can find a gap around the Dec. 20 even in the average for all file size categories. medium: 100MB ~ 1GB large: 1GB ~ Tomoaki Nakamura ICEPP, Univ. of Tokyo

  14. Profiles (2011-09-01 ~ 2012-07-01) Extracted only average points. Average throughput have been decreased 30~40% after Dec. 20, 2011 as compared to before. small: 0 ~ 100MB ~2011-12-20 0.7MB/sec → 0.5MB/sec (70%) medium: 100MB ~ 1GB 5.1MB/sec → 3.1MB/sec (60%) large: 1GB ~ 12.9MB/sec →8.5MB/sec (66%) Tomoaki Nakamura ICEPP, Univ. of Tokyo

  15. Sites (50% down after 2011-12-20) small: 0 ~ 100MB down less than 50% down greater than 50% medium: 100MB ~ 1GB large: 1GB ~ To extract sites which has bad connectivity after Dec. 20, all sites are separated as two groups by the 50% threshold of the reduction rate. Tomoaki Nakamura ICEPP, Univ. of Tokyo 15

  16. Bad connectivity (● down greater than 50% after 2011-12-20, ●Tier1,●FR-Tier2) • large: 1GB ~ • down less than 50% • but data points < 10 • AUSTRALIA-ATLAS_DATADISK • CSTCDIE_DATADISK • ILLINOISHEP_DATADISK • IL-TAU-HEP_DATADISK • ITEP_DATADISK • JINR-LCG2_DATADISK • OU_OCHEP_SWT2_DATADISK • RO-02-NIPNE_DATADISK • RO-14-ITIM_DATADISK • RO-16-UAIC_DATADISK • RU-MOSCOW-FIAN-LCG2_DATADISK • RU-MOSCOW-SINP-LCG2_DATADISK • RU-PNPI_DATADISK • RU-PROTVINO-IHEP_DATADISK • SE-SNIC-T2_DATADISK • TECHNION-HEP_DATADISK • TOKYO-LCG2_DATADISK • TR-10-ULAKBIM_DATADISK • WEIZMANN-LCG2_DATADISK • small: 0 ~ 100MB • AUSTRALIA-ATLAS_DATADISK • BEIJING-LCG2_DATADISK • BNL-OSG2_DATADISK • CA-ALBERTA-WESTGRID-T2_DATADISK • CA-MCGILL-CLUMEQ-T2_DATADISK • CA-SCINET-T2_DATADISK • DESY-HH_DATADISK • DESY-ZN_DATADISK • FZK-LCG2_DATADISK • ITEP_DATADISK • JINR-LCG2_DATADISK • NET2_DATADISK • OU_OCHEP_SWT2_DATADISK • RO-02-NIPNE_DATADISK • RRC-KI_DATADISK • RU-PNPI_DATADISK • SFU-LCG2_DATADISK • SLACXRD_DATADISK • SWT2_CPB_DATADISK • TAIWAN-LCG2_DATADISK • TOKYO-LCG2_DATADISK • TRIUMF-LCG2_DATADISK • medium: 100MB ~ 1GB • AUSTRALIA-ATLAS_DATADISK • BNL-OSG2_DATADISK • CA-ALBERTA-WESTGRID-T2_DATADISK • CA-MCGILL-CLUMEQ-T2_DATADISK • CA-SCINET-T2_DATADISK • CYFRONET-LCG2_DATADISK • DESY-HH_DATADISK • DESY-ZN_DATADISK • HEPHY-UIBK_DATADISK • IN2P3-LPC_DATADISK • INFN-FRASCATI_DATADISK • INFN-MILANO-ATLASC_DATADISK • INFN-NAPOLI-ATLAS_DATADISK • ITEP_DATADISK • JINR-LCG2_DATADISK • LIP-LISBON_DATADISK • LRZ-LMU_DATADISK • MPPMU_DATADISK • MWT2_DATADISK • NET2_DATADISK • NIKHEF-ELPROD_DATADISK • OU_OCHEP_SWT2_DATADISK • PRAGUELCG2_DATADISK • RO-02-NIPNE_DATADISK • RO-07-NIPNE_DATADISK • RO-16-UAIC_DATADISK • RRC-KI_DATADISK • RU-MOSCOW-FIAN-LCG2_DATADISK • RU-MOSCOW-SINP-LCG2_DATADISK • RU-PNPI_DATADISK • RU-PROTVINO-IHEP_DATADISK • SFU-LCG2_DATADISK • SLACXRD_DATADISK • SWT2_CPB_DATADISK • TAIWAN-LCG2_DATADISK • TOKYO-LCG2_DATADISK • TRIUMF-LCG2_DATADISK • UKI-LT2-UCL-HEP_DATADISK • UKI-NORTHGRID-SHEF-HEP_DATADISK • UKI-SCOTGRID-GLASGOW_DATADISK • UKI-SOUTHGRID-BHAM-HEP_DATADISK • UKI-SOUTHGRID-RALPP_DATADISK • UNI-FREIBURG_DATADISK • large: 1GB ~ • BEIJING-LCG2_DATADISK • CA-ALBERTA-WESTGRID-T2_DATADISK • CA-MCGILL-CLUMEQ-T2_DATADISK • CA-SCINET-T2_DATADISK • CYFRONET-LCG2_DATADISK • DESY-HH_DATADISK • HEPHY-UIBK_DATADISK • INFN-MILANO-ATLASC_DATADISK • LIP-LISBON_DATADISK • LRZ-LMU_DATADISK • MPPMU_DATADISK • NET2_DATADISK • PRAGUELCG2_DATADISK • RRC-KI_DATADISK • SFU-LCG2_DATADISK • SLACXRD_DATADISK • SWT2_CPB_DATADISK • TRIUMF-LCG2_DATADISK • UKI-LT2-UCL-HEP_DATADISK • UKI-NORTHGRID-LIV-HEP_DATADISK • UKI-NORTHGRID-MAN-HEP_DATADISK • UKI-NORTHGRID-SHEF-HEP_DATADISK • UKI-SCOTGRID-GLASGOW_DATADISK • UKI-SOUTHGRID-BHAM-HEP_DATADISK • UKI-SOUTHGRID-RALPP_DATADISK • UNI-FREIBURG_DATADISK Only far sites are categorized as bad connectivity group. All sites in France except for the IN2P3-LPC indicates good connectivity (see next page). Sites listed in right hand side are excluded from the good connectivity group due to the lack of data points. Small number of data points must be originating from the timeout in the DDM sonar. Tomoaki Nakamura ICEPP, Univ. of Tokyo

  17. Sites (● down less than 50%) • medium: 100MB ~ 1GB • AGLT2_DATADISK • BEIJING-LCG2_DATADISK • CA-VICTORIA-WESTGRID-T2_DATADISK • CERN-PROD_DATADISK • CSCS-LCG2_DATADISK • CSTCDIE_DATADISK • FZK-LCG2_DATADISK • GOEGRID_DATADISK • GRIF-IRFU_DATADISK • GRIF-LPNHE_DATADISK • IFAE_DATADISK • IFIC-LCG2_DATADISK • ILLINOISHEP_DATADISK • IL-TAU-HEP_DATADISK • IN2P3-CC_DATADISK • IN2P3-CPPM_DATADISK • IN2P3-LAPP_DATADISK • IN2P3-LPSC_DATADISK • INFN-ROMA1_DATADISK • INFN-T1_DATADISK • LIP-COIMBRA_DATADISK • NCG-INGRID-PT_DATADISK • NDGF-T1_DATADISK • PIC_DATADISK • RAL-LCG2_DATADISK • RO-14-ITIM_DATADISK • SARA-MATRIX_DATADISK • SE-SNIC-T2_DATADISK • TECHNION-HEP_DATADISK • TR-10-ULAKBIM_DATADISK • UAM-LCG2_DATADISK • UKI-LT2-QMUL_DATADISK • UKI-LT2-RHUL_DATADISK • UKI-NORTHGRID-LANCS-HEP_DATADISK • UKI-NORTHGRID-LIV-HEP_DATADISK • UKI-NORTHGRID-MAN-HEP_DATADISK • UKI-SCOTGRID-ECDF_DATADISK • UKI-SOUTHGRID-CAM-HEP_DATADISK • UKI-SOUTHGRID-OX-HEP_DATADISK • WEIZMANN-LCG2_DATADISK • WUPPERTALPROD_DATADISK • large: 1GB ~ • and data points > 10 • AGLT2_DATADISK • BNL-OSG2_DATADISK • CA-VICTORIA-WESTGRID-T2_DATADISK • CERN-PROD_DATADISK • CSCS-LCG2_DATADISK • DESY-ZN_DATADISK • FZK-LCG2_DATADISK • GOEGRID_DATADISK • GRIF-IRFU_DATADISK • GRIF-LPNHE_DATADISK • IFAE_DATADISK • IFIC-LCG2_DATADISK • IN2P3-CC_DATADISK • IN2P3-CPPM_DATADISK • IN2P3-LAPP_DATADISK • IN2P3-LPC_DATADISK • IN2P3-LPSC_DATADISK • INFN-FRASCATI_DATADISK • INFN-NAPOLI-ATLAS_DATADISK • INFN-ROMA1_DATADISK • INFN-T1_DATADISK • LIP-COIMBRA_DATADISK • MWT2_DATADISK • NCG-INGRID-PT_DATADISK • NDGF-T1_DATADISK • NIKHEF-ELPROD_DATADISK • PIC_DATADISK • RAL-LCG2_DATADISK • RO-07-NIPNE_DATADISK • SARA-MATRIX_DATADISK • TAIWAN-LCG2_DATADISK • UAM-LCG2_DATADISK • UKI-LT2-QMUL_DATADISK • UKI-LT2-RHUL_DATADISK • UKI-NORTHGRID-LANCS-HEP_DATADISK • UKI-SCOTGRID-ECDF_DATADISK • UKI-SOUTHGRID-CAM-HEP_DATADISK • UKI-SOUTHGRID-OX-HEP_DATADISK • WUPPERTALPROD_DATADISK • small: 0 ~ 100MB • AGLT2_DATADISK • CA-VICTORIA-WESTGRID-T2_DATADISK • CERN-PROD_DATADISK • CSCS-LCG2_DATADISK • CSTCDIE_DATADISK • CYFRONET-LCG2_DATADISK • GOEGRID_DATADISK • GRIF-IRFU_DATADISK • GRIF-LPNHE_DATADISK • HEPHY-UIBK_DATADISK • IFAE_DATADISK • IFIC-LCG2_DATADISK • ILLINOISHEP_DATADISK • IL-TAU-HEP_DATADISK • IN2P3-CC_DATADISK • IN2P3-CPPM_DATADISK • IN2P3-LAPP_DATADISK • IN2P3-LPC_DATADISK • IN2P3-LPSC_DATADISK • INFN-FRASCATI_DATADISK • INFN-MILANO-ATLASC_DATADISK • INFN-NAPOLI-ATLAS_DATADISK • INFN-ROMA1_DATADISK • INFN-T1_DATADISK • LIP-COIMBRA_DATADISK • LIP-LISBON_DATADISK • LRZ-LMU_DATADISK • MPPMU_DATADISK • MWT2_DATADISK • NCG-INGRID-PT_DATADISK • NDGF-T1_DATADISK • NIKHEF-ELPROD_DATADISK • PIC_DATADISK • PRAGUELCG2_DATADISK • RAL-LCG2_DATADISK • RO-07-NIPNE_DATADISK • RO-14-ITIM_DATADISK • RO-16-UAIC_DATADISK • RU-MOSCOW-FIAN-LCG2_DATADISK • RU-MOSCOW-SINP-LCG2_DATADISK • RU-PROTVINO-IHEP_DATADISK • SARA-MATRIX_DATADISK • SE-SNIC-T2_DATADISK • TECHNION-HEP_DATADISK • TR-10-ULAKBIM_DATADISK • UAM-LCG2_DATADISK • UKI-LT2-QMUL_DATADISK • UKI-LT2-RHUL_DATADISK • UKI-LT2-UCL-HEP_DATADISK • UKI-NORTHGRID-LANCS-HEP_DATADISK • UKI-NORTHGRID-LIV-HEP_DATADISK • UKI-NORTHGRID-MAN-HEP_DATADISK • UKI-NORTHGRID-SHEF-HEP_DATADISK • UKI-SCOTGRID-ECDF_DATADISK • UKI-SCOTGRID-GLASGOW_DATADISK • UKI-SOUTHGRID-BHAM-HEP_DATADISK • UKI-SOUTHGRID-CAM-HEP_DATADISK • UKI-SOUTHGRID-OX-HEP_DATADISK • UKI-SOUTHGRID-RALPP_DATADISK • UNI-FREIBURG_DATADISK • WEIZMANN-LCG2_DATADISK • WUPPERTALPROD_DATADISK Tomoaki Nakamura ICEPP, Univ. of Tokyo

  18. Summary For the transfer from IN2P3-LPC to TOKYO, there are no significant changes in historical viewpoint. The transfer rate itself is not so bad, but the stability is not so good. It seems there is a dependence on several file servers to be used. Settings and parameters for data transfer in all file servers need to be confirmed. I will contact with site admin. of IN2P3-LPC. For the transfer from GRIF-LAL to TOKYO, a dependence of file server is seen especially for two newer file servers in the 1GB file transfer case. However, there are no difference in settings and parameters for all servers according to the site admin. of GRIF-LAL. The throughput from GRIF-LAL have been dropped down for relatively far sites after Dec. 20, 2011 obviously. I don’t know whether it is a result of some network optimization or not. One of the possibilities of the reduction is LHCONE in France. Tomoaki Nakamura ICEPP, Univ. of Tokyo

  19. New site status boad http://dashb-atlas-ssb.cern.ch/dashboard/request.py/siteview#currentView=Sonar&find[pSC][0][sS]=|cnTOKYO&find[pSC][0][bR]=false&find[pSC][1][sS]=&find[pSC][1][bR]=false&find[pSC][2][sS]=&find[pSC][2][bR]=false&find[pSC][3][sS]=&find[pSC][3][bR]=false&find[pSC][4][sS]=&find[pSC][4][bR]=false&find[pSC][5][sS]=&find[pSC][5][bR]=false&find[pSC][6][sS]=&find[pSC][6][bR]=false&find[pSC][7][sS]=&find[pSC][7][bR]=false&find[pSC][8][sS]=&find[pSC][8][bR]=false&find[pSC][9][sS]=&find[pSC][9][bR]=false&find[pSC][10][sS]=&find[pSC][10][bR]=false&find[pSC][11][sS]=&find[pSC][11][bR]=false&find[pSC][12][sS]=&find[pSC][12][bR]=false&find[pSC][13][sS]=&find[pSC][13][bR]=false&find[pSC][14][sS]=|nen/a&find[pSC][14][bR]=false&find[pSC][15][sS]=&find[pSC][15][bR]=false&find[pSC][16][sS]=&find[pSC][16][bR]=false&find[pSC][17][sS]=&find[pSC][17][bR]=false&find[pSC][18][sS]=&find[pSC][18][bR]=false&find[pSC][19][sS]=&find[pSC][19][bR]=false&find[sS]=and&find[bR]=true&highlight=false DDM Sonar perfSONAR This SSB shows the throughput by “DDM sonar” and “perfSONAR” in one line, and it makes it possible to compare easily both data. Tomoaki Nakamura ICEPP, Univ. of Tokyo

  20. An example to check the site connectivity Basically they have a good correlation each other except for the no data points about the DDM sonar (0 value). The low value of perfSONAR throughput for FZK is due to the measurement via the firewall in FZK. Since a point for TAIWAN→TOKYOseems to deviate from the correlation band, the data transfer throughput might be not so good in spite of the good network connectivity. For GRIF-LAL, the data points indicating slow value are not included due to the timeout presumably for the case of large file transfer. Data points are extracted from the new SSB. Jun. 18, 2012 15:00 UTC TOKYO-LCG2 vs. AGLT2 BNL-OSG2 CA-SCINET-T2 CERN-PROD DESY-HH FZK-LCG2 GRIF-LAL INFN-NAPOLI-ATLAS LRZ-LMU PIC PRAGUELCG2 SARA-MATRIX TAIWAN-LCG2 TRIUMF-LCG2 ● To TOKYO ● From TOKYO Sonar Average Byte Rate Large Files DDM Sonar: AvgBRL [MB/s] GRIF-LAL FZK GRIF-LAL TAIWAN Average Throughput from perfSONAR perfSONAR: AvgThr [MB/s] Tomoaki Nakamura ICEPP, Univ. of Tokyo

More Related