Queries regarding caching

[devysh1907]

Why redis is required to run superset, what will happen if we dont enable it.

[dosubot[bot]]

Redis is not strictly required to run Superset. If Redis is not enabled, Superset uses a built-in cache that stores data in the metadata database. This fallback mechanism is used for required caches like Filter State and Explore caching. The built-in cache can also be configured to store other data, such as chart data, using the SupersetMetastoreCache ^[1][2].

However, using Redis can improve performance and scalability by efficiently caching various functionalities, such as dashboard filter states, chart form data, and SQL Lab query results ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[dosubot[bot]]

Could you clarify what you mean by "default cache timeout of emails"? Are you referring to the cache duration for email-related data, or is it related to how long email tasks are stored in the cache before being processed? Any additional context would be helpful.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[devysh1907]

@dosu
Where do we set connection pool count if deploying superset using helm

[dosubot[bot]]

Could you provide more details about which connection pool you are referring to? Are you asking about the connection pool for the database, Redis, or another service? Any additional context about your deployment setup would be helpful.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[devysh1907]

@dosu
talking about both redis and databse

[dosubot[bot]]

To configure the Redis connection pool settings in the Superset Helm chart, you can override the default values in the values.yaml file. The Superset Helm chart relies on the bitnami/redis chart, so you can specify Redis settings in your custom values.yaml file. Here's an example configuration:

redis:
  master:
    persistence:
      enabled: false
    resources:
      limits:
        cpu: 100m
        memory: 256Mi
      requests:
        cpu: 100m
        memory: 256Mi
  replica:
    replicaCount: 1
    persistence:
      enabled: false
    resources:
      limits:
        cpu: 100m
        memory: 256Mi
      requests:
        cpu: 100m
        memory: 256Mi

You can adjust the resources and replicaCount settings according to your requirements. This configuration should be added to your my-values.yaml file, which you then use when installing or upgrading the Superset Helm chart:

helm upgrade --install --values my-values.yaml superset superset/superset

For more specific Redis connection pool settings, refer to the bitnami/redis chart documentation for available configuration options ^[1].

Unfortunately, I couldn't find specific information on configuring the database connection pool settings in the Superset Helm chart. You might need to explore the database configuration options in the values.yaml file or consult the database's Helm chart documentation for guidance.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}