Skip to content

Latest commit

 

History

History
77 lines (68 loc) · 4.42 KB

2022-03-21.md

File metadata and controls

77 lines (68 loc) · 4.42 KB

2022-03-21

Agenda

  • DICOMweb performance

    • multi-part mime vs single part for video
    • Is single part API new?
    • What is the fastest way to download entire study in DICOM P10 format from DICOMweb
      • Some people are calling the study or series multi-part mime API /studies/studyuid /studies/studyuid/series/seriesuid
      • This is not ideal for the following reasons:
        • The maximum download rate over a single connection is limited. (e.g. 100 Gbps, you might get 2 Gbps with this method)
          • TCP is chatty and this is noticeable at high bandwidths
          • TCP Window Size Limitations/issues configuring
        • Server needs to "build" the multi-part mime response
          • should be able to stream it
          • can use a lot of memory if your not careful (need to retrieve several in parallel but not all)
        • Client needs to "parse" the multi-part mime response
          • Requires lots of things to go right to avoid massive delays and memory usage
          • Not allow HTTP Body to be accessed until entire response read
          • Client environment limitations on buffer sizes (e.g. browsers limit arrays to 4GB RAM)
          • To do this right:
            • Need stream based network API
            • Need stream based multi-part mime parser
            • Need code that can make sense of streamed instances
      • Better to use HTTP/2 and make concurrent requests
        • Requires a smart DICOMweb implementation
          • DCM4CHEE / frame endpoint is slow at extracting individual frames from a DICOM P10 instance
            • Bill has a test digital pathology image with 32,000 frames in one SOP Instance - takes 60 seconds on DCM4CHEE
            • This could be resolved by storing indexes of each frame to avoid seeking from beginning each time
      • Speed mainluy depends on how the service was implemented
  • DICOMweb WG27 Activities

    • Relative URI CP
      • Standard as written does not say you can't use relative URIs, so you have to fall back on the standard it references to understand what it means
      • This CP defines this explicitly
        • All metadata requests are relative to the study root (e.g. studies/$studyuid)
    • JPEG-XL Work Item
  • DICOM QIDO-RS Study Query in memory project

  • DICOM Test Data Generator

  • MIMIC data sets