Startup Optimization

[JPercival]

Currently, the cqf-ruler takes around 30 seconds to start up on my local laptop. Ideally, this would be significantly faster. <10 seconds would be ideal.

There are several different things we could do to optimize this:

• Eliminate all Spring warnings on startup

There are a number of startup warnings that could potentially affect startup speeds:

WARN o.s.b.a.o.j.JpaBaseConfiguration$JpaWebConfiguration [JpaBaseConfiguration.java:219] spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning

INFO o.s.b.web.servlet.RegistrationBean [DynamicRegistrationBean.java:110] Servlet dispatcherServlet was not registered (possibly already registered?)

• Add the ability to selectively enable functionality

  • Scheduling
  • Supported resource types
  • Making sure plugins enabling/disabling are documented

• Add explicit Spring configuration as opposed to component scanning

  • This should be coordinated with Smile efforts to do the same for the base hapi-fhir-server
  • Need to make sure plugin scanning still works

• Precompute Spring config

  • Not sure if this would work or not. Need to explore possible options. One possible solution is to go full Spring-native, but there are quite a few runtime things in hapi and the ruler that might break.