Libpacks in BIMcloud take long time to load

[Jaime-airc_digital]

Since the change to library packs, the loading times of BIMcloud libraries has increased more than 10 fold. See video below comparing the same template loading libraries from BIMcloud both in Archicad 27 and 28. While Archicad 27 loaded the same libraries in around 20 seconds, in Archicad 28, using libpacks, the total library loading time of approximately 2 minutes and 33 seconds just to open a single project template.

This loading time also happens when refreshing the libraries. This is a very long wait time for a user to begin working or update libraries.
Please provide feedback, as this is a serious problem that I suppose most Archicad 28 users have been facing in silence.

[Lingwisyer]

I am assuming this is a full library sync you are performing? I have only ever seen that downloading dialogue when first joining a computer to TW... So the equivilent of downloading one large file vs multiple smaller files totalling the same size?

Their reasoning is that if there is an update to a libpack, you would only be updating the individual libpack rather than the entire monolithic library. Though there is, or was, the issue of the lack of a system to actually compare libpack versions automatically on a TW server which made this "advantage" a moot point... Not sure if this has since been addressed...

Ling.

[Jaime-airc_digital]

Hi Ling,

What we experience is that this dialog appears every time we open a BIMcloud project or a Project that is using BIMcloud libraries (not just on the first load of the BIMcloud projects). It also appears when updating the libraries, for example when loading an IFC file. It is very disruptive to have to wait almost 3 minutes every time.

[Lingwisyer]

For clarification, is this Basic or SAAS / Collaborate?

[Jaime-airc_digital]

Hi Ling, we are paying for Software as a service BIMcloud with 7 licenses.

[MMontgomery]

Have you found any resolution?

Our office has been dealing with the same issue.    We experience extremely long load times on AC28 Teamwork and PLN files that use the BIMcloud libpacks and legacy libraries. 

We can open a project, then get up and go make coffee before it opens.

[Jaime-airc_digital]

We have found it to be a problem specific to Apple systems, a colleague working on the same BIMcloud project using Windows has not experienced the issue.

[Kornel Beleznai]

Hello all,

I'm sorry to hear about this issue related to the BIMcloud library handling slowness, and thank you for raising it here on Community.

The longer loading time is indeed coming from the new, global library handling system. When you share a project for the first time, by default, all the global library packages will be shared on BIMcloud as well, which takes more time than with the previous library management. This also affects the loading times when you manage these libraries later, when the project is already shared on BIMcloud.

Product Management is aware of this situation, and our Support Team escalates every report about the issue to them, so that they can evaluate the impact properly. According to this, they are investigating the possibilities to improve on this workflow; however, I don't have further information about the developments at the moment.

Until the problem is resolved from the development side, I can recommend the following workaround option to reduce the processing time during the library-related actions in Teamwork:

Try to load only those libpacks into your projects that are indeed necessary for the design. For example, a project in the European region might not need the 'Japanese Architecture' or the USA-specific libpacks. It's worth going through the Archicad Library Packages folder with this approach and excluding/deleting the unnecessary ones. You can always download these packages from the Graphisft website if they are needed later.

If you have any further questions or comments regarding this topic, feel free to reach out to us through the support channels, where we can investigate and handle individual issues and cases more efficiently.

Once again, apologies for the inconvenience this issue might cause, and thank you for your understanding.

Kind regards,
Kornél