Open jcfr opened 1 year ago
After integrating updates into the main branch, it takes ~10mins to fully deploy the updated website.
Some of the large files copied during each deployment could be moved into a "Resource" release.
Files are associated with Project Week 28, 35, 37 and 38 takes close 0.5GB.
$ du -ah . | sort -hr | head -n 20 1003M . 244M ./PW38_2023_GranCanaria/Projects 244M ./PW38_2023_GranCanaria 174M ./PW37_2022_Virtual 173M ./PW37_2022_Virtual/Projects 136M ./PW28_2018_GranCanaria 121M ./PW28_2018_GranCanaria/Projects 113M ./PW35_2021_Virtual/Projects 113M ./PW35_2021_Virtual 100M ./PW38_2023_GranCanaria/Projects/SlicerLiver 100M ./PW37_2022_Virtual/Projects/SlicerLiver 83M ./PW33_2020_GranCanaria 72M ./PW31_2019_Boston 70M ./PW33_2020_GranCanaria/Projects 69M ./PW30_2019_GranCanaria 62M ./PW35_2021_Virtual/Projects/US_CT_VertebraRegistration 59M ./PW35_2021_Virtual/Projects/US_CT_VertebraRegistration/US-CTAlignment.gif 54M ./PW30_2019_GranCanaria/Projects 52M ./PW31_2019_Boston/Projects 44M ./PW38_2023_GranCanaria/Projects/MultiSpectralSensorIntegration
$ find . -type f -printf '%s %p\n'| sort -nr | head -20 | while IFS= read -r line; do size=$(echo $line | cut -d" " -f1); file=$(echo $line | cut -d" " -f2); printf $size | numfmt --to=iec; echo " $file"; done 59M ./PW35_2021_Virtual/Projects/US_CT_VertebraRegistration/US-CTAlignment.gif 33M ./PW38_2023_GranCanaria/Projects/SlicerLiver/distance-tumor.webm 33M ./PW37_2022_Virtual/Projects/SlicerLiver/distance-tumor.webm 32M ./PW38_2023_GranCanaria/Projects/SlicerLiver/planning.webm 32M ./PW37_2022_Virtual/Projects/SlicerLiver/planning.webm 24M ./PW28_2018_GranCanaria/Projects/3DViewsLinking/myimage.gif 24M ./PW38_2023_GranCanaria/Projects/MultiSpectralSensorIntegration/TEEV2+PCOUV.gif 23M ./PW37_2022_Virtual/Projects/StreamlinedROIAnnotationTool/FinalROITool_1.gif 21M ./PW38_2023_GranCanaria/Projects/MultiSpectralSensorIntegration/TEEV2PCOUV-2.gif 20M ./PW38_2023_GranCanaria/Projects/SlicerLiver/distance-vessels.webm 20M ./PW37_2022_Virtual/Projects/SlicerLiver/distance-vessels.webm 20M ./PW30_2019_GranCanaria/Projects/Data-glove_for_virtual_operations/20190201_095221.gif 16M ./PW31_2019_Boston/Breakouts/DataManagement/XNAT 15M ./PW38_2023_GranCanaria/Projects/MONAILabel2bundle/monai_bundle_vs_total_seg_spleen.gif 15M ./PW33_2020_GranCanaria/Projects/ClubFoot/Models/stage3.vtk 15M ./PW31_2019_Boston/Projects/ClubfootCasts/Models/stage3.vtk 14M ./PW38_2023_GranCanaria/Projects/MONAILabel2bundle/monai_bundle_vs_total_seg_idc.gif 14M ./PW37_2022_Virtual/Projects/SlicerTMS/tms_vis.gif 14M ./PW38_2023_GranCanaria/Projects/KaapanaFastViewingAndTaggingOfDICOMImages/NA-MIC.gif 14M ./PW38_2023_GranCanaria/Projects/SlicerLiver/liver_resection.mp4
After integration of #640, overall time to build&deploy went from ~10mins to ~6.5mins:
Deploy speed is looking pretty good now, ~3 mins
Is your feature request related to a problem? Please describe.
After integrating updates into the main branch, it takes ~10mins to fully deploy the updated website.
Describe the solution you'd like
Some of the large files copied during each deployment could be moved into a "Resource" release.
Files are associated with Project Week 28, 35, 37 and 38 takes close 0.5GB.