Not a developer here. I have a custom parent record with 40 calculated custom fields (standard deviation and averages) based on the values from the related child custom records. This data is critical to us, so I’m hoping I can update the values real time via scripting. So I’m thinking that when I create/edit/delete a child record, the related parent record’s 40 calculated fields will be automatically updated (real time). So far, the maximum child record values that we may have is 20 per parent record. Would this be an issue performance-wise (40 calculated fields)?

It depends, if there is a search or other process other than the computation. It can be a factor that will lead to slow process. However, if the calculation is just simply (+) (-) then I don't think there are impact on this.

its an issue performance-wise if your developer does 1 search per child record or loads each one

Thank you both. In the UI, the 40 calculated values can be achieved through ONE summary saved search with at least 40 columns (one for each calculated value). Sounds like it's gonna work fine if done this way and loaded just once in the script.