The remote client immediately fetches data from a running (not solving) Fluent server session. However, when the solver is running the client cannot fetch data immediately. The remote client can only communicate with the solving Fluent server when the current iteration is over. For example, if an iteration takes 5 seconds, then the remote client will take at least 5 seconds to fetch the data after you make the request.

While a remote client can connect to multiple Fluent server sessions, for best performance you should try to have the connected server machines be running simulations that take a similar amount of time for calculating.

If a machine has multiple IP addresses, you should set the REMOTING_SERVER_ADDRESS to an outward facing IP address, both on the client and server machines so that they can communicate with each other.

By default, both the remote client and Fluent server session have a 3 minute timer for completing a communication between the two machines. If the communication is not completed within the 3 minutes, then the remote client and the Fluent server will disconnect from each other. You can reconnect the session. If the communication timeout persists, you can control the timeout by setting the REMOTING_CONNECTION_TIME_OUT environment variable.

For better performance, you should disconnect the Remote Visualization Client from the Fluent server session, if you are not actively monitoring the solution on the client.