-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Volume Testing on the FHIR Core client app #3181
Comments
Device Specs
WiFi - 20Mbps Results
|
@Mstjamush Can you explicitly define the time format for the starts shared above? e.g. HH:MM:ss |
@ellykits it's in HH:MM:ss format |
@Mstjamush can you share the same results for 10k households please? |
@pld Let me generate the HHs and share |
Findings investigating the MWCore app:
|
Observation on the Search Query:
Opportunities for improvement
|
Ticket to track performance optimizations on the FHIR SDK engine - google/android-fhir#2547 |
For the form loading, after profiling MWCore made the following observations for the Registration form:
We can implement a caching mechanism for the resources once loaded the first time and figure out an appropriate cache invalidation mechanism. This can be informed by various factors like we don't expect Questionnaire resources to change frequently during use. |
For the page registers, after doing some further tests, we've realized that there are three types of queries that are run
The last two are the most costly, since they'd need to go through entire db rows to get the total count. Also, to note, is that all queries in the sdk are wrapped within db transactions. From Room's documentation
So, a query can seem to take long because it's queued and waiting for other transactions to finish. That is, regardless of whether the queries are in different coroutines, and were running concurrently. |
Separate ticket to track select query being queued, instead of running concurrently: google/android-fhir#2552 |
Device Specs
_WiFi - 20Mbps Results
|
Tests after refactors Device Specs
_WiFi - 20Mbps Results
|
Tests after refactors Device Specs
_WiFi - 20Mbps Results
|
Tests after refactors (Includes cache on forms) Device Specs
_WiFi - 20Mbps Results
Save forms has a questionnaire issue |
was this performed on a version of the SDK with this PR included? https://github.com/google/android-fhir/pull/2565/files |
No, the sdk versions didn't include the PR...we instead used chunking of the parameters from the app's side to prevent the error |
Tests after refactors (Includes cache on forms) Device Specs
_WiFi - 20Mbps Results
@Gental-Giant the issue was fixed |
Interesting that load time jumped up so much |
Update July 1st 2024
|
@ndegwamartin Can you provide an update on this ? Aug 5th CC @Mstjamush |
Device Specs
|
All the profiling under this ticket are covered so closing this. We can open another ticket once we target a new profiling. |
Overview
We need to conduct Volume Testing to see how the app scales with a lot of data. This testing will help highlight the various bottlenecks with the app.
Initial Test Data
We can gradually increase the data set size as we optimize and improve.
Tasks
The text was updated successfully, but these errors were encountered: