Thank you for your post.
There are many things that affect performance. It is mostly about the layouts and what tables are being referenced. There is a cache, but with a lot less memory and processing speed on an iPhone/iPad compared to a Mac, some resources are shuffled in and out at varying times.
Thanks for the info. What part of a table is the issue. Is it the number or records, number of layouts, number of objects, etc? In a situation when the table is in the background and the data is pulled via a relationship is there still overhead from the data file.
All of your points could be a factor. For example, if you have 1000 fields, it will take longer to access the data than if you had 10 fields. If there are 1000 objects on a layout, it will take longer to render than if you had 10 objects. It will take a bit longer to access record 5,000 (out of 10,i000) than it would to access record 5 (out of 10). A portal with one record and two fields will be a bit quicker than a portal with 10 records and 10 fields, although the information will be quick to access due to the index.
In other words, there are a lot of factors involved. If the data being pulled is in the background, then you probably won't notice any difference. The data being displayed would be more apparent. This applies to FileMaker Pro in general.