Meeting: | SPARC OS Technical Committee |
|---|---|
Date: | 01/18/2023 |
Time: | 3:01 pm - 3:57 pm |
MUSC | Greg, Evan, Brigette |
Iowa | |
LA CaTS | Ying |
Children’s National | |
Case Western | Jeremy |
OHSU | Erik, Imogen |
Stony Brook Medicine |
...
Ying reported also seeing the PDF access error, seemingly related to the Paperclip story.
...
MUSC:
1/18/23
Evan was introduced as a new team member assisting with technical tasks related to reporting and database. Members will be hearing from him as we gather their institutional SPARC reports.
Working on SPARC Release 3.10.1 mini release - see current stories.
New story additions & development ended 1/12/23
Release date 1/26/23
3.4.0 SPARC Fulfillment stories as the next major release.
New story additions & development ends 3/2/23
Release Date 3/16/23
Brainstorming SPARC speed/performance issue solutions. Asked attendees if they have experienced similar issues with SPARC or another product and suggested areas to look into.
Erik recommended focusing on high areas of impact first, reducing the data and number of rows queried (threw out active record), look at number of columns queried (change index for null data), figuring out a small unit of info to display to reduce the load at once, reviewing logs for underlying issues, looking at places with multiple loops and seeing activities happening for necessity for completing all actions. This takes time to do, and there are commercial services that can monitor and generate data if necessary to go that route.
Jeremy agreed with looking at active query time records and database scaling.
Audit trail - inquired if anyone has pulled out an audit trail from their SPARC instance to share a script. Noone has had to do this yet
...