In my original scaling testing, we could easily handle 10s of thousands of records (I don't recall at what point I stopped testing, but it was well above 100k, I think).
Many features have gone in since then, so probably one of them (most likely, summary computations) is slowing the application down.
If you hit a slowdown with real-world data and you have access to Spin Control (in the developer package), please send us the log it emits. If you don't have access to Spin Control, you can gather a sample from the command line.
- Find the process number of your OmniFocus using Activity Monitor or 'ps' in Terminal
- Type 'sleep 5; sample my-pid 10' in Terminal, hit return
- Start repeatedly doing the slow action in OmniFocus until Terminal returns from the sample
- Mail me the file it emits along with a description of what you were doing (tjw at omnigroup dot com) or send it to
omnifocus@omnigroup.com. If you can include your OmniFocus app support directory and preferences, so much the better.
Thanks for the help tracking this down!