BimCloud SaaS speed & performance

[BoldArch]

We have transitioned to Bimcloud SaaS in the last 3 months for all new projects (AC27 - 29), after using a locally hosted Bimcloud Basic server for 10+ years (still operating a few old AC27 projects).  All users (approx. 6 simultaneous users at most) have noted that certain operations take an excessive amount of time, within projects hosted on the cloud server.  Namely joining a project, send/receive actions, release all actions, library loading/modifying actions. 

For comparison, we have projects in excess of 3Gb on the local server, and a project less than 300MB on the cloud server.  Joinery the large project on the local server is a 2 minute operation, compared to 9 minutes taken to join the small project on the cloud server.  Send/receive function is a similar - a 1 minute exercise, compared to a 4 minute exercise. 

Other than obvious downtime waiting for these actions, this has also led to poor practice by the users - send/receiving less frequently, etc.  Which in turn has resulted in a few cases of exaggerated data loss.  Slow speed isn't an excuse for bad practice, but still frustrating.

Note we have also upgraded our internet speed in the last 2 weeks, from a 100up/75down service, to 1,000up/450down, at point of supply.  Speed tests at individual PCs tend to achieve an average at 865down/430up. Obviously a massive upgrade, however seems to have had no effect on the above operations. 

Has anyone else noted similar when comparing Bimcloud Basic to Bimcloud SaaS?  Any solutions?

[Lingwisyer]

https://community.graphisoft.com/t5/Teamwork-BIMcloud/Would-like-feedback-regarding-network-speed-fo...

[Roderick_Anderson]

Going through exactly the same questions at this moment. I am being asked to make a decision to convert our permanent licenses to subsciption licenses and need to make this decision in the next 5 days. I've requested a test BimCloud SaaS and started testing today. So far not impressed and our test users at least from the first day of testing, feel that these basic teamwork functions are taking too long:

• Send/Receive
• Reserving attributes (pretty much with any attribute)
• Reserving views/layouts
• Reserving/making changes to publisher sets
• Releasing all

Today one of our staffers was late to a personal appointment because the normal Send/Receive then Release All process that is normal procedure at the end of the day that normally takes a minute or so, took over 10 minutes which is excessive.

10 minutes X 8 people X + - 300 days = 400 wasted hours per year.....  = the cost of several servers!

I'm hoping our testing goes better, but so far it's not looking good.