70MB is a rather large file and the Nvidia Quatro M4000 only has 8GB of VRAM out of the box, unless you've tweaked it. We regularly run 3D models at 20-40MB but have had some exceed 1GB using that same card, and if we try to manipulate a 3D shaded view performance suffers. Setting the view style to 2D wireframe massively improves performance. If you just must orbit a shaded view, you should consider amping up your VRAM.
Some suggestions for handling large files
-Make sure views are 2D wireframe prior to manipulating the view. (investigate Navisworks and the NWNAVIGATOR.arx for shaded views)
-Save preset VIEWs to quickly navigate to specific locations without dragging a 3D view around in ORBIT.
-For some reason manipulating views in PS viewports is much less robust than doing so in MS, so manipulating viewpoints and saving VIEW's in MS provides better performance, VIEW's can then be restored in PS viewports.
-Use layer family sets to minimize what's being displayed at any given time, freezing unneeded layers will improve performance.
-Investigate the use of blocks for sub-assemblies to reduce file size. Rule of thumb, if the components are used more than twice, make them a block.
-Investigate XREF's to minimize file size, they aren't just for collaboration. Large models can be broken up into smaller sections based on geographic locations or processes or disciplines or assemblies or any host of intelligent divisions making the entire model process faster. Large assemblies can be treated like blocks and OVERLAY'ed numerous times (locations and orientations (even different scales)) in the same model. All models could then be appended to a Navisworks session and viewed together (published to an NWD for viewing with the FREE Navisworks Freedom). XREF's also provide an enhanced level of flexibility when making drawings, allowing background assemblies or discipline specific models to be layer controlled separately in individual viewports.
Just some ideas .....