Please see below message from Kuali regarding the latest performance issues. As the first priority outlined below, Kuali is temporarily scaling back previously published validation enhancements. If you run into any problems with validations in your protocols, please contact email@example.com and someone from the ERA team will quickly help you address it.
Thank you for your continued patience during this time.
Barbara Inderwiesche, CRA
Director, Electronic Research Administration
I’m reaching out with an update to our Protocols community on performance issues in the software that have been impacting many of our customers.
We’re at a point in the growth of the use of our Protocols product where inefficiencies in key areas of the code are causing performance issues (lag and slowness in the application). The severity of the performance issues are being felt across our whole customer base, but they are particularly acute for institutions that have either a very high volume of protocol submissions or a very complex protocol template with lots of progressive disclosure logic built into the form and a heavy reliance on the list gadget. In some circumstances, the performance issues are making it really hard for end users to complete their tasks in the software.
Why is this happening now?
The use of our product has increased exponentially over time, and we’re at a threshold where we need to make some changes in order to scale effectively. In addition, we recently released enhancements to validations in the list gadget, and an unintended consequence of those enhancements has been degraded performance in the list gadget.
What is Kuali doing about it?
Over the past few weeks, we’ve been making improvements to inefficient areas of the code, but depending on the volume and template configuration at your institution, the work we’ve done so far may not have resulted in improved performance for your end users. We’ve also changed the way our instances autoscale so that our infrastructure can respond more quickly to an increased load at different times of the day. We’re still tuning the timing and characteristics of the scaling to make sure we can be responsive very quickly to periods of increased usage.
We have much more work to do to solve the problem fully, however. Here are our next steps:
We believe that each of these steps will materially improve performance, and once they are all completed, the application will be very performant.
What should I do if I have questions?
If you have any questions, please feel free to reach out to me directly. I’d be delighted to hear from you.
Thank you to everyone who has submitted feedback about the performance problem. In many cases, this feedback was instrumental in helping us diagnose the different issues contributing to the overall problem. We’re sorry for the impact system slowness has had on your end users, and we’re grateful for your partnership as we work through this complex set of issues.