Just completing a project that has been deployed into a global SF Org. We have one object in particular that is likely to require a large number of records and is a related list on most pages.
At what point is this likely to have an impact on page performance? Since lookup and master fields are indexed, I'm assuming that perfomance is pretty much optimised by default for related lists?
The first product migrated to this app added 220K records to this particular object, and that's likely to grow at around 20%/year through on-going business. The originally targeted migration was for 6 products comprising around 2.2M records and the intention is that several 10s of products are added to the platform in the future. So the number of records could easily grow to several million records.
Is this a worry and if so does anyone have any best practices to share?