Determine partitioning strategy for content and file tables

[bjester]

Current behavior

As studio usage has grown, database tables have grown to a size that makes performance optimization very difficult. The size makes queries or joins against these large tables very slow and therefore user operations to feel slow.

Desired outcomes

• Determine a strategy for partitioning the ContentNode and File database tables:
  • How many buckets should we initially define for each?
  • What's the best field to partition the File table?
  • What's the best way to migrate to partitioned structures?
• Perform some manual testing if possible