Yves,
I would suggest to send contact your support center and provide them gdc log files - they will give you all information.
There is no known performance issue - we have usually faster results with later versions.
There is one parameter that may have an impact:
we introduced some checks in GDC to verify that another fglrun is not connecting to it. We added some "security levels" that allows you to configure these checks. By default, GDC expects to see some identifiers in the connection hand shake (they are set up when starting your application via shortcuts and @FGLxxx commands). If you don't use this mechanism, there is no identifier, and GDC will warn the user that an unknown connection is attempted.
For that, we check the remote host name and IP, using reverse DNS (a system call). We noticed that this system call can take up to 5 seconds if your DNS is not correctly configured on your network.
As we don't have much details, I would suggest you (in addition to check with your support center) to:
- lower GDC security level to 0 and check again. If this is immediate => this is likely to be the reason.
- use shortcuts and @FGL tags and check again, if this is not the case.
Hope this helps,
Pierre-Nicolas
