Hi Kevin,
Since I'm encountering almost same thing, I thought I'd share this (I'm not proposing a solution though).
This is happening in a document with tens of millions of records and a pretty complex data model.
What I noticed is that if I don't have any selections made when saving, the response time of QV after the save is actually done (date modified attribute of the file is updated) is quite high (around 5 minutes).
In addition, when QV gets back to responding, the file gets also updated another time (an updated date modified).
So what you may try, is to have some selections made before saving, it might reduce your 30-minute wait.
This may also depend on the cpu power since it's gets fully consumed (response time may be affected).
Another tip, try not to force-close QV when saving as it might corrupt the file (well, I remember this happened once with one of the customers and the document had to be replaced from a backup copy).
Hope that someone could also share his ideas that would be helpful to all.
