Basically what the title says. How much harm is there that transient fields are not annotated with ‘"indexed:false’" ?
Hi @jasper-silent-root ,
Questions about performance in A12 are notoriously hard to answer. The main reason is that projects can put different numbers and sizes of models, documents, attachments and links in, and what is ok for one project might be problematic for another. There are also other dimensions (parallel users, complexity of extension points or other computations). A12 recommends a defensive approach to minimize the loss of performance as a basic principle of development. What we are trying to achieve is to start with an optimized system so that when it scales up, the performance is already optimized. What we would like to avoid is starting with an inefficient setup which behaves just fine in the early phase but is not ready for scaling. This way you might end up in a situation where you will need better performance, but your application is built around inefficient bases, so updating it will be very costly.
The Data Services recommendation is to index the minimal set of fields that are required for your requirements. You can test the system by creating 10x–20x the data with this setup, and if it behaves in a satisfactory manner, you can do it.
This answer is valid for all DS versions up till 39.1.0
Cheers,