Instead of having Knack’s database automatically processing every hour each SUM, MIN, MAX, AVERAGE and COUNT fields of a given object, users should be able to to define that rate (with a minimum value = hourly rate) for each field.
Users should also be able to configure if these fields should be processed while creating or updating a field. For example, a user could create a record without having a COUNT field computed upon creation but, say, once a day. The field would then be computed in the future according to the rate defined on the field’s schema level.
This would ease the load on Knack’s servers and give users more flexibility. Win win for all.