Re-evalute block cache sizing on M30 and M40 tiers

ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Critical - P2
    • None
    • Affects Version/s: None
    • Component/s: Block Cache
    • None
    • Storage Engines - Persistence
    • 60.92
    • None
    • 5

      Now that we've seen some usage out in the real world, there's some appetite for re-evaluating the block cache sizes on these tiers.

      See comments for more details, and why this is high-prio.

      The scope here is to re-run the testing done for these tiers (see coments), but with a 2GB WiredTiger cache, and re-evaluate if the block cache size should actually be 2GB instead of the current 768MB.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Will Korteland
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: