When designing solutions that can provide the performance we aim for, we sometimes have to sacrifice other less important features.

In our latest update of our workflows app, we have removed the ability to sort on several of the fields. Previously, users were able to sort on any fields. But.. most options were very rarely or never used. And one can still filter on any of the fields.

By limiting the number of columns the users can sort on, the performance of the app is improved. This and other speed-focused improvements has good huge iimpact on the  overall performance of the app.

Columns like severity and UID are still sortable, as we know that these columns are useful to be able to sort on. And we can ensure that these fields are well indexed, ensuring speedy response.

And why can't we just add more indexes, making all fields possible to be sorted.....? There are multiple reasons for that; storage, index maintenances impacting over all system performance, slower write / update operations.

Another change we did was to update the Filter By (available when clicking on the funnel icon). In many cases the count of the values is not interesting, so by default we do not show them. However, the numbers are just a click away.

The count of records for the different values are by default not shown, but is just a click away

We are working through the other apps as well, applying improvements to performance by evaluering the need for speed versus the features relevance.