topic Re: Very Slow Send/Receive in Teamwork & BIMcloud

Very Slow Send/Receive

Anonymous — Fri, 06 Nov 2009 17:53:53 GMT

When we first started sharing the project (3 of us) it would take about 5-15 seconds to send/receive. Now all of the sudden it takes 3 plus minutes of wheel spinning! Could this be a glitch or a setting that I accidentally changed? The status bar shows complete then goes away, then I'm left watching the spinning wheel for 3 more minutes. It's very frustrating and slow, anyone know a fix?

Thanks.

Re: Very Slow Send/Receive

Anonymous — Fri, 06 Nov 2009 20:30:35 GMT

We are experiencing the same problem. The only difference is that 2 out of the 4 team members are experiencing the extremely slow send and receive times. Two users are fine. They all appear to be set-up identically and have identical Mac computers. If you find the answer please let me know.

Brian

Re: Very Slow Send/Receive

Anonymous — Fri, 06 Nov 2009 20:36:02 GMT

Yes, We are kinda getting the same results. Only 1 of us (Me) has the long S/R time.

We are all using iMacs 2.8GHz Intel Core 2 Duo w/ 2GB SDRAM (minimum). Two of the identical machines are acting differently time wise.

Re: Very Slow Send/Receive

Karl Ottenstein — Fri, 06 Nov 2009 20:41:25 GMT

There is no way to answer this question if you don't say what version of AC / etc you are using! I find it hard to believe that what you are experiencing is in AC 13 with TW2, so you must be in an earlier version?

Thanks,
Karl

Re: Very Slow Send/Receive

Anonymous — Fri, 06 Nov 2009 20:44:07 GMT

Oops, sorry, I forgot that part.

We are using AC 13 w/ TW2.

OS 10.5.8

Re: Very Slow Send/Receive

Anonymous — Fri, 06 Nov 2009 20:46:39 GMT

We are using AC13 with TW2 on Mac Intels running 10.5. About to change to 10.6.

Re: Very Slow Send/Receive

Karl Ottenstein — Sun, 08 Nov 2009 01:43:12 GMT

Are all users in each of your situations in the office on the LAN?

Is everyone in the same subnet? And, perhaps everyone plugged into the same switch? Do the affected users have any other network problems - have you tested transferring a really large file (some 100's of MB) to each workstation to verify that each has the same speed connection to the machine that is hosting the BIM Server?

Thanks,
Karl

Re: Very Slow Send/Receive

Anonymous — Mon, 09 Nov 2009 15:25:21 GMT

Karl,

To respond for Brian, all of our users are on the LAN, same subnet and same switch. We have seen no other network issues with any of our users, and have verified the speed to each.

We actually have 4 users on the project, including myself(admin) with the BIM Server running on my machine, but will soon be moving this to the server (now that we have received 10.6 Server). 3 of the 4 users, including myself, are having speed issues with receiving. Archicad seems to send quickly and the "Processing Progress" window completes and disappears within 30 seconds, but then we get the pinwheel for up to 3-4 minutes before we can start working in the project again.

Hope this helps in some way.

Re: Very Slow Send/Receive

Anonymous — Mon, 09 Nov 2009 18:45:30 GMT

Karl,

I'm getting the same results as Brian. Send/receive is fast, about 10 seconds, then 3-4 min. of spinning wheel.

No other problematic issues with speed for any of the computers on our network, just this Archicad issue.

Could the speed have anything to do with loading libraries? I tried "reload project from server" feature and that changed nothing. In the library report it shows 6,500 duplicates but so does a coworkers computer and he has no issues with send/receive.

FYI- I did make sure Airport is turned off, I'm working on a gigabit network.

Re: Very Slow Send/Receive

Karl Ottenstein — Mon, 09 Nov 2009 19:00:45 GMT

OK, now I understand. I saw a lot of the spinning beach ball after the S/R appeared to have completed during testing, too. I thought that GS was addressing whatever was causing it.

At first I thought that AC was busy computing how to merge the new information it received, but Activity Monitor showed no activity. That made me suspect that there was some kind of 'handshaking' going on with AC waiting for something.

If this is what you see - network activity followed by CPU mostly idle during the beachball period - then definitely contact tech support. They'll probably need a 'support package' generated right after you regain control - as it will contain the log files that indicate what was going on...

Bummed to hear about your experiences.

Karl

Re: Very Slow Send/Receive

Erika Epstein — Mon, 09 Nov 2009 19:04:15 GMT

What happens when you get rid of the duplicates?

Re: Very Slow Send/Receive

Anonymous — Mon, 09 Nov 2009 19:53:09 GMT

No duplicates in our file, I will contact tech support.

Thanks Karl.

Re: Very Slow Send/Receive

Anonymous — Mon, 09 Nov 2009 21:21:12 GMT

Thanks for your help Karl.

I will contact tech support and post what happens back here, to help others that may have this issue.

Re: Very Slow Send/Receive

Anonymous — Mon, 09 Nov 2009 21:22:37 GMT

Erika wrote:
What happens when you get rid of the duplicates?

I haven't resolved the duplicate issue yet, but the other users have the same duplicates and they don't have the spinning wheel long wait time.

Re: Very Slow Send/Receive

Dennis Lee — Fri, 13 Nov 2009 23:01:07 GMT

One thing you can try:

1. Make note of EXACT bim server name from the bim server. "bimserver.xxx.xxx".

2. Make sure when you first browse for teamwork project, first identify yourself to the correct bimserver. If the exact name doesn't come up automatically, ADD the bimserver name exactly as in #1. Then put in your id and password. Make sure you don't identify yourself to other names like "computer name" or "bimserver.xxx.xxx (computer name)" that pops up automatically.

3. After identifying yourself to the correct named server, browse for projects using the same method, from the correct named server. Don't open projects under server names such as "computer name" or "bimserver.xxx.xxx (computer name)".

4. After opening the project, make sure that all the bim server libraries loaded to the project are from the correct named bim server. From the manage bim server libraries dialog, I believe only the first few words of the server name will be visible next to the name of the library. If they are showing for example "Project Library computer" or something like that, get rid of all the libraries from the wrong named server and reload the libraries to the correct named bim server.

For some reason, the name that you type in when you configure the bim server doesn't show up by default when identifying, browsing, adding library. I believe having a consistent EXACT bim server name for all phases of the signin process is crucial. Otherwise, even though maybe they are referring to the same folder on the computer, it slows things down a lot.

Just my 2 cents after long couple of nights wrestling w/ the BS (bim server of course).

It might be worth a try.

Re: Very Slow Send/Receive

Anonymous — Tue, 17 Nov 2009 10:38:42 GMT

Thanks Dennis, I'll give that a shot and post what happens.

Re: Very Slow Send/Receive

Anonymous — Thu, 14 Jan 2010 20:28:24 GMT

We have been having the same problem with AC13. Some machines work fine with others having S?R times of over 13 minutes. TS has not been of help yet.

We have tried a brand new quad core machine and no improvement. The slow machines have a long period of cpu inactivity, a short spike, and then another long period of nothing. We have sent support packages to GS and we are now sending them a PLN.

Had our network checked and we are all on gigabit with a brand new quad core x-serve. It is definitely not the hardware as one of the oldest machines is the fastest.

Re: Very Slow Send/Receive

Anonymous — Fri, 15 Jan 2010 18:12:49 GMT

Update:
I received a response from Graphisoft. This is what they told me:

The slowness appears to be due to message handling. You can try this as a worker round this somewhat by deleting request and the like from your messages and completed task areas.

Best Regards,

Sean Fennelly
Help Desk Agent, GRAPHISOFT

I've been working on solo projects recently so I haven't been able to test their suggestion.

Re: Very Slow Send/Receive

Anonymous — Fri, 15 Jan 2010 20:45:02 GMT

Did all this occur with the latest build of archicad? If it has, I would try this and see if there is a decrease in the "handshaking" afterwards. Use the IP address of the BIM Server instead of the name. This has cured our inability to see the Libraries in the new version with the added benefit of seeming a little bit snappier. Let us know if that helps.

*edit.... just noticed you were on build 3000. I would still try the IP address and see if it helps.

Re: Very Slow Send/Receive

SeaGeoff — Fri, 15 Jan 2010 21:59:51 GMT

We have just the opposite experience as Marlon, i.e. I switched to using the name of the BIM Server not the IP. This after having some suddenly abnormal S/R delays and libary problems. (I can't remember why I started with the IP in the first place except that maybe the generate link function automatically set it that way.)

In our case the slowdown was no doubt the result of having DHCP generated IP addresses. The IP eventually changed and things went south. Changing to name based linking, and relinking the libraries as well, fixed things. Since we are accessing the BIM Server only over the LAN this arrangement works fine.