search

looker-open-source / look-at-me-sideways

A style guide and linter for Looker's LookML data modeling language
MIT License
123 stars 37 forks source link

New rule(s): warning against excessive numbers of certain objects (models?) that can cause perf issues #155

Open fabio-looker opened 8 months ago

jakerohald commented 8 months ago

Hey @fabio-looker, can I get some more context on what rule your thinking about here?

fabio-looker commented 8 months ago

Hi @jakerohald ! It's somewhat of a placeholder that needs some research. In the past, having too many of certain objects (e.g. models, or dimensions) could lead to performance issues on the Looker server when parsing projects for the first time since a deployment or when loading an explore into memory.

However, I believe these are largely fixed by the "new LookML runtime", so some due diligence is needed on my end before actually recommending any limits. If you have any experiences to share, with the new LookML runtime enabled, I'm all ears!

jakerohald commented 8 months ago

Hey @fabio-looker, no experience with the new LookML runtime, but keeping track of this incase the issue rears its head for our work.

jakerohald commented 7 months ago

@fabio-looker - our org has started to experience pretty significant performance issues when operating in dev mode - particularly around Looker being unable to load objects on the initial go, perhaps this issue could be attributed to the issue raised above? Interested to hear your thoughts.

fabio-looker commented 7 months ago

Hi @jakerohald ! Could I ask for a bit of extra detail: