View the original community article here
Last tested: Jan 19, 2021
Does the explore in question have a lot of fields and joins? If so, the current advice is that we should reduce the number of fields and joins in an explore until it's "small" enough" but we don't have a specific target.
One thing to note is that hiding some of the fields with the
hidden parameter or the
fields parameter would not help much because our backend would still have to do a lot of work to gather all the data from all the LookML files referenced in the explore.