Cache configuration

LearningNinja
LearningNinja Member
in Federated

Hello Folks,

I understand for a Federated Connection, the DOMO cards will fire queries directly to Snowflake. However, I have few questions around this:

  1. Will there be any cache stored at card level?
  2. Will there be any cache stored at user account / user session level?
  3. Will there be any cache stored in DOMO for my connected Federated Dataset?
  4. Will there be any cache set based on the cards browsed (irrespective of the users)?

Also, how will the Time-to-live (TTL) impact the cache mechanism? Apart from these, are there any other areas I should be looking at in terms of Cache and Performance tuning of dashboards?

Thanks in advance.

Tagged:

Best Answers

  • JoshMillheim
    JoshMillheim Domo Product Manager
    Answer ✓

    Hi @LearningNinja!

    1. The cache for federated queries will save the query results for a specific query for up to 24 hours (this is the TTL mechanism and is configurable by user)
    2. Cache is stored at the query level on card queries, and only caches query results. Because this cache is at the query level, if multiple users view the same card in Domo that produces the same query under the hood, then those query results could be returned for multiple users.

      If using an OAuth configuration for your federated connection that requires users to authenticate to the cloud warehouse before it can return queries, those queries result caches would not apply across users, as each user potentially has different levels of data access.

      Data previews on the dataset details page are not cached
    3. See above
    4. See response for #1

  • JoshMillheim
    JoshMillheim Domo Product Manager
    Answer ✓

    @LearningNinja - Editing the TTL on an existing federated connection should clear the cache.

Answers

  • JoshMillheim
    JoshMillheim Domo Product Manager
    Answer ✓

    Hi @LearningNinja!

    1. The cache for federated queries will save the query results for a specific query for up to 24 hours (this is the TTL mechanism and is configurable by user)
    2. Cache is stored at the query level on card queries, and only caches query results. Because this cache is at the query level, if multiple users view the same card in Domo that produces the same query under the hood, then those query results could be returned for multiple users.

      If using an OAuth configuration for your federated connection that requires users to authenticate to the cloud warehouse before it can return queries, those queries result caches would not apply across users, as each user potentially has different levels of data access.

      Data previews on the dataset details page are not cached
    3. See above
    4. See response for #1

  • LearningNinja
    LearningNinja Member

    @JoshMillheim - Thanks for providing detailed information around cache. Is there any mechanism available on DOMO to clear the cache created from Federated connection? Something like a force flush?

  • JoshMillheim
    JoshMillheim Domo Product Manager
    Answer ✓

    @LearningNinja - Editing the TTL on an existing federated connection should clear the cache.

Categories