Understanding BIG_GAP and TurnOffGAPs in Revit Journal Files

Verma7UKV3
Contributor

Understanding BIG_GAP and TurnOffGAPs in Revit Journal Files

Verma7UKV3
Contributor
Contributor

Hello everyone,

I recently came across some entries in my Revit journal files and I'm trying to understand what they mean. Specifically, I encountered the following lines:

 

' 13.831051!!! 2:!!!BIG_GAP DesktopStorageLogic::onFileSaveToCentral Save to Central
' 35.698169 1:<<DesktopStorageLogic::onFileSaveToCentral Save to Central/ALL_GAPS 19.466493/TurnOff_GAPs 80%

 

From what I've gathered, these entries seem to indicate significant delays or gaps during the "Save to Central" process. Here is my understanding so far:

  1. BIG_GAP:

    • The BIG_GAP annotation suggests a notable delay or interruption during the save process.
    • The timestamp (13.831051 seconds) shows that this delay occurred at that point in the operation.
  2. TurnOffGAPs:

    • The TurnOff_GAPs 80% indicates that a significant portion (80%) of the save process time (19.466493 seconds) was spent in these gaps or delays. This could imply that only 20% of the time was actively used for saving, while the rest was waiting or idle time.

I'm looking for confirmation if my understanding is correct and any additional insights into these terms. What are the common causes of these delays and how can they be mitigated?

Thanks in advance for your help!


0 Likes
Reply
418 Views
1 Reply
Reply (1)

vitorbortoncello
Advisor
Advisor

Your understanding is correct...

Network latency or interruptions can cause significant delays during operations that require communication with central files on a network server.

Large file sizes and complex models with numerous linked files can increase the time needed to save or synchronize changes.

 

  • Using a wired connection instead of Wi-Fi can help reduce network-related delays.
  • Regular maintenance on both the server and workstations can improve performance.
  • Breaking down large models into smaller linked files where feasible can reduce complexity and file size.
  • Regularly purging unused elements and auditing models helps keep them optimized.

 

 

If this helped, please like this post and mark accept solution!

A resposta te ajudou? Não esqueça de curtir e aceitar como solução!


Vitor Bortoncello | Arquiteto | Especialista BIM


aAutodesk Certified Professional