Menu

#4419 Database and Code Optimizations

OSCAR Main Trunk
closed
None
5
2016-09-16
2016-09-07
No

While using master, it has been observeed that the following applications in OSCAR require speed optimization: the eChart, Inbox, Tickler list, Consultation List and OSCAR Messages. Additionally McMaster is moving to using the mysql cluster for OSCAR's database. The change to casemgmt_note table reflects the ability to stripe data across data nodes. In this case each demographic's notes will be stored on one data node. For example, demographic 1's notes will be on node 1 and demographic 2's notes will be on node 2 and so on. This is accomplished by using the primary key for notes to include the unique note id and the demographic_no. This change will have a neutral impact on InnoDB and MyISAM storage engines.

The other changes to code and queries will noticeably improve performace for any storage engine. The inbox has been streamlined as well as the loading of consultation lists and tickler lists. The queries for OSCAR messages have been optimized.

Discussion

  • Raymond Rusk

    Raymond Rusk - 2016-09-07
    • status: open --> open-rejected
    • Priority: 8 --> 1
     
  • Raymond Rusk

    Raymond Rusk - 2016-09-07

    File this as a properly documented feature request.

     
  • Randy Jonasz

    Randy Jonasz - 2016-09-08

    This commit does not introduce any new features. Rather it optimizes both the code base and database for OSCAR.

     
  • Randy Jonasz

    Randy Jonasz - 2016-09-08
    • status: open-rejected --> open
    • Priority: 1 --> 5
     
  • Sarah Allen

    Sarah Allen - 2016-09-16
    • status: open --> closed
     
MongoDB Logo MongoDB