Revit Architecture Forum
Welcome to Autodesk’s Revit Architecture Forums. Share your knowledge, ask questions, and explore popular Revit Architecture topics.
abbrechen
Suchergebnisse werden angezeigt für 
Anzeigen  nur  | Stattdessen suchen nach 
Meintest du: 

Compacting Central File sync time

3 ANTWORTEN 3
Antworten
Nachricht 1 von 4
richardsachs4475
551 Aufrufe, 3 Antworten

Compacting Central File sync time

I am finding that when compacting with a sync to central that it is taking a significant amount of time - like 30 or more minutes for a 300 mb file. I used to do this regularly- once or a week or so and if a normal sync takes 1 minute - it might take 2 or 3. This has been the case in Revit 2017-2019. Since encountering this problem I have stopped doing it but was asked today to try it again and having the same result. This is standard Revit- not cloud hosted or Revit server. As far as I know there is nothing usual about our network or server. Anyone else experienced this or have any thoughts as to why this might be happening?

3 ANTWORTEN 3
Nachricht 2 von 4
Anonymous
als Antwort auf: richardsachs4475

I stopped compacting central files years ago as they will go up again within a few syncs.

 

If you do have to compact the model...detach from central, compact and then save the file as a different name...then repeat again and save back as the original name.  That might save you 30-50mb, but really, if hard drive space is a concern I would suggest looking at SSD upgrades strictly for project files.

Nachricht 3 von 4
richardsachs4475
als Antwort auf: Anonymous

I've seen 100 or mb of reduction or more and better performing model overall, whenever we got close to 500 mb start to see problems. Granted file size isn't best measure of project performance but see no reason to deal with an unnecessarily large model.
I now mostly replace models periodically having found this compact time to be untenable. But that is more disruptive to the team than compacting used be. It always goes back up with new activity but typically takes a while to get back to the pre-compacted size. But when I was able to this, say, weekly the model never got so far out of hand. But regardless, still doesn't answer the question as to why this is happening. If it's broken I will stop trying to use. If it's some issue with my firm's network/server or my machine I'd be curious to know what the possible contributing factors might be.
Nachricht 4 von 4
Anonymous
als Antwort auf: richardsachs4475

Performance wise...it is better to fix the warnings vs compacting or purging.  The "Why" it compacts for a while and then jumps up again may be the history of the central file.  When you save as a new name and compact it is essentially resetting the history, but then again the "open worksets and close worksets" trick is still perplexing.

 

But I used to work with 750 mb to 1.5 gb models and was amazed that they performed well.  Model I am working on currently is 740 mb and works quite well....except for the fact that it has 1100+ warnings.  Guess I know what I will be doing later this week.

 

 

 

 

Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.

In Foren veröffentlichen  

Autodesk Design & Make Report