Large Lists and Distributed Cache: Blob, Page Output, and Object

I have a large list of 70000 items. Viewing the list throws a header javascript error "Unable to set property '_onDestroy' of undefined or null".We've addressed it several ways: increasing CA application thresholds, adding indexes and stripping down views, etc. The list is presented in datasheet view by default. We're discussing breaking the content into flattened folders of 5k items each but that has complexity. Publishing Features are enabled at the site and web levels.

Another angle is caching. It seems somewhat promising, but I wanted to verify that these strategies are what I think they are and what any real-world caveats are, and what might be combined in my case. http://blogs.msdn.com/b/kunal_mukherjee/archive/2011/01/10/caching-in-share-point-2010-best-practice.aspx

BLOB: I'm familiar enough with the BLOB concept, but primarily when it comes to files of a certain size (large) and of specified extensions (eg: .mp4 files over 10gb) to cheaper storage outside SQL. This is a list of columns containing text, with no large attachments I'm aware of, so not sure what I can expect to gain in this specific case. I don't think it would hurt.

Page Output: Seems more promising, caching rendered aspx pages client-side reduces the SQL calls and WFE load because page layout and content do not need to be rerendered. Sounds good. This list, however, is updated daily, so content will need to be updated. Also, this seems to work ideally with anonymous access. This list is secured to few users.

Object caching: Server-side caching, I assume XML or some kind of index that shortcuts some of the work SQL would have to perform to present the data. Hard to think of a downside in my case, but maybe I'm missing something.

Much thanks as usual!

Scott