# Performance of Formulas vs Rules? **URL:** \ **Category:** Get Help\ **Created:** [December 12, 2024, 8:31pm UTC](https://community.fibery.io/t/performance-of-formulas-vs-rules/7943 "2024-12-12T20:31:42Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![drew](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/drew/32/10581_2.png) [@drew](https://community.fibery.io/u/drew)\ **Post date:** [December 12, 2024, 8:31pm UTC](https://community.fibery.io/t/performance-of-formulas-vs-rules/7943/1 "2024-12-12T20:31:42Z")
I’m building a giant financial analyzer where each entity requires ~200 calculated results. My question is: Should I create Formula fields for each calculation (most intuitive/straightforward approach), OR should I create Rules to update ~200 _editable_ fields as needed (seemingly more efficient, but maybe not)? I guess I don’t understand exactly how/when formulas get triggered for recalculation. Presumably initial load times would be much faster with ‘static’ fields, but I don’t like the UX of showing editable fields that are actually/functionally calculated instead. I should note that we’re not talking about ‘simple’ math operations either, but rather heavy use of the Power function to recreate [missing] CUMIPMT and CUMPRINC equivalents for various mortgage/loan scenarios. Appreciate any insights & guidance! 🙏 ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [December 12, 2024, 8:35pm UTC](https://community.fibery.io/t/performance-of-formulas-vs-rules/7943/2 "2024-12-12T20:35:41Z")
How many entities you will have in a database with these heavy formulas? ---
**Author:** ![drew](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/drew/32/10581_2.png) [@drew](https://community.fibery.io/u/drew)\ **Post date:** [December 12, 2024, 8:46pm UTC](https://community.fibery.io/t/performance-of-formulas-vs-rules/7943/3 "2024-12-12T20:46:28Z")
68 as of today, but I’ll be adding 1 or 2 daily as I continue analyzing more & more multifamily apartment deals for potential acquisition & management. Thanks for asking! \*Oh also, each entity has another ~100 truly editable fields, so about ~300 fields in total. AND each parent entity has several children (related subtables for itemizing income, expenses, rehab, etc., actual-v-proforma), but they’re much simpler & negligible computationally. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [December 12, 2024, 8:49pm UTC](https://community.fibery.io/t/performance-of-formulas-vs-rules/7943/4 "2024-12-12T20:49:56Z")
You should be safe with formulas then. For 10K+ entities and 200 formulas maybe it would be not so good, but for this amount it should be pretty safe. However, I am not sure we have accounts with 200 formulas per database, so you will be a pioneer here. ---
**Author:** ![drew](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/drew/32/10581_2.png) [@drew](https://community.fibery.io/u/drew)\ **Post date:** [December 12, 2024, 8:53pm UTC](https://community.fibery.io/t/performance-of-formulas-vs-rules/7943/5 "2024-12-12T20:53:02Z")
Love it, thanks Michael! Then let the full build-out begin… 🧑‍🚀🚀 ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [December 13, 2024, 6:43am UTC](https://community.fibery.io/t/performance-of-formulas-vs-rules/7943/6 "2024-12-13T06:43:01Z")
One note. We have fields limit per database, you can have no more than 300 fields in total in a single database