[Brian]

Okay, setting up a test database with just over 2000 projects, I can see what you're seeing here. For what it's worth, a database with 3000 actions is far more responsive than one with 2000 projects, so rearranging things in some manner should help.

(For each of those projects, we have code that looks at it, figures out which action is the next action, apply the style, and so forth. Actions have a lower resource overhead associated with them, basically.)

I'll write this up as a performance issue, but yeah; this use case definitely stretches what the app was designed to handle a bit. :-)