Does Document Save History reduce model opening time or reduce hang-ups? How to remove it? [HUGE MODLE OPENING TIMES AND SYNC TIMES]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hello Revit Aficionado's,
I have a challenge for you!
We have been facing a few very long model opening times (~35-50 mins) out of which a huge chunk is just the Revit UI frozen with a blue spinny circle waiting for a response or something. The same happens for syncing. We tested this out by picking up on Sync Start and Sync End events in the Revit API and then a Revit Idle event when the UI is ready. The Sync ends and then the blue spinny circle is back for another 15~20 minutes taking the total sync time to around 30 mins.
This is creating a lot of workflow issues as each user has to sync and wait for potentially 45 minutes to get back to work and also delaying other syncs for other users after them.
Reaching out to Autodesk, they pointed out some issue with our Document Save Histories showing up in log files for some of our linked files. But no resolution was suggested by them and they don't really know why this long of an opening or sync times (just say its shorter on their end when we gave them the model access).
Anybody know what this Document Save History in the log files actually means and how to remove it if its slows down loading and sync times.
'C 02-Jul-2024 10:37:43.936; 8:< The current load request is an automated one.
' 7:< Document save history --> :
' 7:< Revit 2014 - Preview Pre-Release 2014 (2014.000) : 20130123_1540(x64)
' 7:< Revit 2014 2014 (2014.000) : 20130308_1515(x64)
' 7:< Revit 2014 2014 (2014.000) : 20130709_2115(x64)
' 7:< Revit 2014 2014 (2014.000) : 20131024_2115(x64)
' 7:< Revit 2015 2015 (2015.000) : 20140223_1515(x64)
' 7:< Revit 2015 2015 (2015.000) : 20140606_1530(x64)
' 7:< Revit 2015 2015 (2015.000) : 20150303_0715(x64)
' 7:< Revit 2015 2015 (2015.000) : 20151208_0715(x64)
' 7:< Revit 2015 2015 (2015.000) : 20160120_0715(x64)
' 7:< Revit 2015 2015 (2015.000) : 20160220_0715(x64)
' 7:< Revit 2015 2015 (2015.000) : 20151008_0715(x64)
' 7:< Revit 2017 2017 (2017.000) : 20170118_1100(x64)
' 7:< Revit 2017 2017 (2017.000) : 20170816_0615(x64)
' 7:< Revit 2017 2017 (2017.000) : 20171027_0315(x64)
' 7:< Revit 2018 2018 (2018.000) : 20170927_1515(x64)
' 7:< Revit 2018 2018 (2018.000) : 20180329_1100(x64)
' 7:< Revit 2018 2018 (2018.000) : 20180423_1000(x64)
' 7:< Revit 2018 2018 (2018.000) : 20181011_1500(x64)
' 7:< Revit 2019 2019 (2019.000) : 20181217_1515(x64)
' 7:< Revit 2019 2019 (2019.000) : 20190225_1515(x64)
' 7:< Revit 2019 2019 (2019.000) : 20190808_0900(x64)
' 7:< Revit 2019 2019 (2019.000) : 20210416_1515(x64)
' 7:< Revit 2019 2019 (2019.000) : 20211029_1515(x64)
' 7:< Revit 2019 2019 (2019.000) : 20220224_1700(x64)
' 7:< Revit 2022 2022 (2022.000) : 2433f98
' 7:< Revit 2022 2022 (2022.000) : 20220123_1515(x64)
' 7:< Revit 2022 2022 (2022.000) : 20210224_1515(x64)
' 7:< Revit 2022 2022 (2022.000) : 20220520_1515(x64)
' 7:< Revit 2022 2022 (2022.000) : 20230505_1515(x64)
' 7:< Revit 2022 2022 (2022.000) : 20230915_1530(x64)
' 7:< Document save history <--
' 3.024850 7:<<[Cloud]postLoadDocument/ALL_GAPS 0.450719/Threshold_GAPs 23%
This is just one example of a linked model save history, we have 4 more like this in the same model opening with different version histories (some limited to 2018) some going further back.
Any help or suggestions are welcome!
