Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Speed up searches (TRUNK-1750)
    1. Search for patient by ID (TRUNK-1616) *not yet measured*
    2. Searching for a Provider (TRUNK-1664) *not yet measured*
    3. Searching for the location (TRUNK-1665) *not yet measured*
    4. Searching for concepts (TRUNK-1663) *not yet measured*
  2. Speed up the Cohort Builder (RCM-21) *not yet measured*
  3. Speed up ?HTML Form Entry (HTML-58) *not yet measured*
  4. Speed up and improve page loading (TRUNK-1751)
    1. Patient pages occasionally loading improperly (TRUNK-1621) -- will not measure
    2. Speed up loading of pages (TRUNK-28) -- will not measure
    3. Speed up "Edit Encounter" page (TRUNK-1740)
  5. Speed up the patient dashboard (TRUNK-1667) *not yet measured*
  6. Speed up schema design page (TRUNK-1623) *not yet measured*
  7. Speed up modules by caching JavaScript files (TRUNK-1613)
  8. Speed up reporting (TRUNK-1752)
    1. Data exports (RCM-20) *not yet measured*
    2. BIRT Reports (BIRT-30) *not yet measured*
    3. Reporting Module (TRUNK-1754) *not yet measured*
  9. Speed up workflows (TRUNK-1753) -- will not measure
    1. Adding a new program and state (TRUNK-22)
    2. Ending a program with a terminal state (TRUNK-24)
    3. Editing drug orders (TRUNK-25)
    4. Mother to child relationship (FORM-105)
  10. Enhanced caching (TRUNK-434) *not yet measured*

We will build a module for 1.8 performance testing to isolate widgets/features for testing purposes. (http://tickets.openmrs.org/browse/TRUNK-1766TRUNK-1766)

Suggestions

  1. Javascript files provided by modules are not cached? (probably fixable, medium priority) - TRUNK-1613
  2. It takes a long time for the patient dashboard to load after you click on a name on the search page (fixable, high priority) - TRUNK-1667
    • TODO: Need explicit targets for performance improvement (either existing features known to be inefficient OR hints from profiling)
    • FYI – Slowness from too many infopath forms fixedin formentry module 4.5.3
  3. Using cohort builder (probably fixable, but needs investigation, medium priority)
    • Searching the list of Patients having observations MALARIA<sup>archive:1</sup> TRUNK-1618
    • Find the list of patient enrolled in a program<sup>archive:2</sup> - TRUNK-1619
    • Patients having an encounter created for them
    • Searching for Admission diagnosis in the past year
  4. Data exports (using old framework) (RCM-20, low priority)
    • TODO: get a real data export that is slow
    • TODO: Jeremy will provide a data export that is used with the anonymized data set
  5. Patient pages occasionally loading improperly - the top summary bar loads but none of the tab data shows up when the page is done loading. After refreshing a few times, the data shows up. (unsure on fixability, high priority) - TRUNK-1621
    • TODO: replicate the error
    • NOTE: This could be fixed by replacing DOJO widgets with jquery widgets (TRUNK-1652 below)
  6. BIRT Reports are slow (documentation problem) - BIRT-30
  7. HTML Forms, especially complex ones, can take several seconds to load. (have example, high priority) - HTML-58
  8. Linking mother to child on encounter forms is a slow mainly due to the number of steps involved - (Requires UI improvements rather than Performance)
    • TODO: Fixed? Jeremy?
  9. Searching for the location on an infopath form taskpane - (TRUNK-1665)
  10. Searching for a Provider - (TRUNK-1664)
  11. Searching for concepts (e.g., in concept search widget of FormEntry taskpane) - (TRUNK-1663)
  12. Improve workflow when adding a new program and state (TRUNK-22, easy, medium priority)
  13. Improve workflow when ending a program with a terminal state (TRUNK-24, easy, medium priority)
  14. Improve workflow when editing drug orders (TRUNK-25)
  15. Generating data sets in the new reporting framework
    • TODO: Need a specific example if we're going to work on this one for 1.8
  16. It takes long time to load the schema in the Schema Design page. (high priority) - TRUNK-1623
  17. Development is very slow: - TRUNK-1666
    • Reloading modules can take many minutes if there are many deployed with dependencies, even if only one class in one module changes
  18. Reduce number of requests between browser and server - (TRUNK-34)
  19. Convert the dojo widgets to jquery widgets - (TRUNK-1652)
  20. Support for multi level database caching - (TRUNK-434)

...