Skip to content

[storage] Check the cache behavior with very wide records #7554

Open

Description

@mihaibudiu

It seems that the caching layer refuses to cache in memory very wide records.
This can lead to performance anomalies for relatively small collections with very wide records.
E.g. for a program that uses ARRAY_AGG() - most of the time is spent in the UPSERT node of the aggregate, which never hits in the cache.

Activity

  1. added
    storagePersistence for internal state in DBSP operators
    on Oct 20, 2026
  2. added theissue type on Oct 20, 2026
  3. ryzhyk commented on Oct 20, 2026

    @ryzhyk
    Contributor

    Note that refusing to cache maybe the optimal behavior at least in some cases. It's not obvious that forcing such records to be cached is always a good idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    storagePersistence for internal state in DBSP operators

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions