This section discusses CustomActivity and its potential impact on performance. Although CustomActivity can have an impact on performance, more often than not performance problems are a result of having too many managed objects in the engine. Therefore, you should always check this first before looking at your custom code for performance problems.
For information on checking the number of objects, see this link.
How to identify if CustomActivity is slow
There are three ways to identify whether CustomActivity is causing problems in your app. Keep in mind that both Screens and Entities contain a CustomActivity function, so you may need to check both depending on which diagnostic approach you are taking.
Common approaches include:
- Measuring all CustomActivity – you can check to see how long CustomActivity is taking. For information on how to do this: FINISH HERE
- Removing loops – you can remove loops in your code to see if they are expensive. FINISH HERE