Hey @Ben_Swanson,
I’m no Coda support, but I know a thing or two about oversize docs since I deal with them in my coda-expert-for-hire practice way too more often than I’d like to. I outlined a lot in the post linked above. There you can see how to figure out the doc size. For more detailed breakdown (i.e. by table) I composed myself a script to inspect that:
Quick actionable steps to reduce doc size:
- Cut down on conditional formatting; ideally remove it wherever you can and replace with emoji or some other colorful labeling. See: This doc is too big to sync - #7 by Paul_Danyliuk
- Cut down on controls: replace sliders etc with numbers, replace formula controls with Text or any appropriate type (e.g. if you have a calculated yes/no checkbox, just replace it with Text type — Coda will still treat it as yes/no but doc size will shrink). See: PSA: The hidden cost of Checkbox column for true/false values
- Cut down on table buttons. The button’s code is replicated for each row. Use approaches like this one instead: Tutorial: Iterator tables (CurrentValue workaround)
- Cut down on crossdoc item references. They take multiple times more space (because of much longer identifiers) than local tables.
ToText()
your Display Columns always. See: Here's a doc size riddle for the community
Also here’s a large thread on big doc perf: Realistic number of rows in a table
Keep in mind that deleting bunch of stuff will only have effect after 12 hours (IIRC), that’s the time when you can still restore deleted rows and they are still stored in the doc.