Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
O Oak-Tree Imaging Environment
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Oak-Tree
  • Medical Imaging
  • Oak-Tree Imaging Environment
  • Issues
  • #31

Closed
Open
Created Aug 20, 2022 by Rob Oakes@roakesOwner

Deploy Sonador Resource Cache and determine extent of speedup

The caching issues and problems seen in Orthanc only manifest in a very large databases. A lot of the work for the implementation of caching features (orthanc-sonador!10 (merged)) came from working with the Osteoarthritis Database. To determine the extent of the speed up and whether the work currently performed has been sufficient, the following test metrics should be bathered:

  • Load time of DICOMweb interface for OAI segmentations: {"PatientName": "*OAI*", "Modality": "SEG"}
  • Query time for example resource queries defined in Sonador Cache Example API Queries
Edited Aug 20, 2022 by Rob Oakes
Assignee
Assign to
Industrial Strength Imaging Platform: Performance Improvements, Scalability, Cloud Deployments
Milestone
Industrial Strength Imaging Platform: Performance Improvements, Scalability, Cloud Deployments (Past due)
Assign milestone
Time tracking