There is more to performance than a light default view, especially if you open to a different view via a frameset.

This is a wordier version of the notes.ini variable "GoFaster = 1" isn't it?

Ben - it's "TurboCharge = 1" :-)

I would possibly vote for this if it were closer to "IBM should work harder on scalability with large view sizes", or something that seemed to reflect the reality of limits. To simply say database size should not have any effect on performance is an unreasonable and unrealizable goal.

There is a sizable body of performance tuning advice out there that should help prevent a drop in performance out of proportion with the increase in db size. In my experience most performance problems stem from bad application design that doesn't account for the way Notes works, as opposed to inherent limitation of Notes itself.

As Ben says, there is no way to avoid SOME performance falloff as db size goes up, so this idea is unrealistic in that sense. I would suggest that any performance-related ideas which get posted target something specific about the way Notes itself could be improved to alleviate common problems. Something like "limit the wait time for displaying a view with lots of documents using Readers fields when the current user has access to only a few of those documents". Right now, when this occurs, Notes can take a long time to find enough documents to fill the screen for such users so the user waits for what seems like very little return.

And there ARE databases out there, vastly bigger then a meager Gig, that perform just fine.