Still not convinced. Although the whole Admin theory seems to make sense, we have done a ton of testing and really don’t think it has anything to do with the Sharing and how long it takes SF to serve up the records. We have 2 visualizations that use similar selection criteria and are accessed via a community user and the data is returned immediately. We have reports that the data is returned immediately, and we have standard SF views that are returned immediately. We even went so far as to add a new text field designated as an External UID which will then get indexed by default by SF and made that the only field in the selection on the Model, same performance. We use another product for Grids/Tables and when creating and viewing them, the data is instantaneous. Wasted way too much time on this but if this is not about how our page is setup, and I am assuming it is not based on the above, and we have a single condition in the model and this is the type of performance, then using a table in communities is simply not an option due to the performance.
