You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I'm seeing a strong performance degredation when trying to create FHIR resources (Appointments in my case) after switching to a recent version of the FHIR engine.
Using a minimalistic app which simply instantiates the FHIR engine and inserts a couple of appointments with fixed IDs into the store I'm seeing the app blocks for up to ~20seconds before I'm getting the successful callback returning the IDs.
The delay was there in previous versions of the library, but doubled starting from 0.1.0-beta05. This is consistent across multiple app runs and hardware devices.
FhirEngineProvider.init(FhirEngineConfiguration(enableEncryptionIfSupported =false,
DatabaseErrorStrategy.RECREATE_AT_OPEN))
val fhir =FhirEngineProvider.getInstance(this)
GlobalScope.launch {
val t1 =System.currentTimeMillis()
println("FHIR: ${fhir}")
withContext(Dispatchers.IO) {
val app1 =Appointment().setId("333")
val app2 =Appointment().setId("444")
val ids = fhir.create(app1, app2)
// using '0.1.0-beta02' to '0.1.0-beta04' this takes approx. 6-7s// starting from '0.1.0-beta05' including current '1.0.0' this doubles to 13-18s println("Appointments created: ${ids} in "+(System.currentTimeMillis()-t1)+"ms")
}
}
Is there any way to enhance performance (e.g. late scanning, ...) by enabling some properties when initializing the engine?
Is this a known issue and can I dig any deeper to see where the app actually spends the biggest amount of time?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I'm seeing a strong performance degredation when trying to create FHIR resources (Appointments in my case) after switching to a recent version of the FHIR engine.
Using a minimalistic app which simply instantiates the FHIR engine and inserts a couple of appointments with fixed IDs into the store I'm seeing the app blocks for up to ~20seconds before I'm getting the successful callback returning the IDs.
The delay was there in previous versions of the library, but doubled starting from
0.1.0-beta05
. This is consistent across multiple app runs and hardware devices.Is there any way to enhance performance (e.g. late scanning, ...) by enabling some properties when initializing the engine?
Is this a known issue and can I dig any deeper to see where the app actually spends the biggest amount of time?
Any help greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions