Skip to main content

Post-processing tools 2023 R2

DVS Server

Last update: 17.04.2023

DVS Server used to receive data from DVS Clients.

DVS Server used to receive data from DVS Clients.

DVS Server

Description of DVS Servers and options

DVS Server

DVS Servers receive data from the DVS Clients. A server can be ran as part of the post processing package (such as EnSight) or within any process as it is part of the DVS API. A server object is always used by the client to connect to a server (if starting a server locally it must be started before connecting with the client). However this server object is only a shell/proxy object unless it is started using dvs_server_start() or DVS::IServer::startup(). If a server isn't started it is assumed another process/thread has started it and it is only used for connecting the client to the real server.

Server Options

Server options are specified by the C API call dvs_server_set_option(), or the C++ API call DVS::IServer::set_option().

Server Option Default Description
CACHE_URI None A URI used to specify cache type, location and filtering options. See Cache URIs for more information.
SERVER_PORT_BASE 50051 The base port to use for a group of servers. Used with SERVER_PORT_MULT to determine the port to listen to. i.e. SERVER_PORT_BASE + (server_num * SERVER_PORT_MULT).
SERVER_PORT_MULT 0 The multiplier to use with server number to increase SERVER_PORT_BASE by. i.e. SERVER_PORT_BASE + (server_num * SERVER_PORT_MULT).
SERVER_SECURITY_SECRET None The secret string to use for a client to connect to this server. If none is specified no secret is needed by the client.
ENABLE_DYNAMIC_SOURCE True Used to force the server into waiting for external data or not. If false only reads from the specified cache.
VERBOSE 0 Verbosity level of the server, Min 0, Max 3.
DVS_FILE_LOCATION Cache location Set the location for the dvs files created when creating datasets. This can be a fully qualified pathname or relative to the root of the cache specified by the CACHE_URI. The internal link stored in the file pointing to the cache location is also controlled by if the DVS_FILE_LOCATION is a fully qualified pathname or relative. If it is fully qualified the link will be fully qualified. Allowing you to move the dvs file around with the cache staying in a static location. If the DVS_FILE_LOCATION is relative, then the internal link will be relative to the cache location. This will allow you to move the cache and dvs files around together and they will still work (recommended).
GRPC_MAX_NUM_RETRIES 3 Sets the maximum number of retries to use if using GRPC. This setting can help if having problems with too many clients going into a small number of servers. This should be used in conjunction with GRPC_BACKOFF_MIN_MS and GRPC_BACKOFF_MAX_MS
GRPC_BACKOFF_MIN_MS 100 The minimum time to wait before attempting a retry
GRPC_BACKOFF_MAX_MS 1000 The maximum time to wait before attempting a retry, the current algorithm is linear and increments each retry by GRPC_BACKOFF_LINEAR_MS until reaching either the maximum number of retries * GRPC_BACKOFF_LINEAR_MS or GRPC_BACKOFF_MAX_MS
GRPC_BACKOFF_LINEAR_MS 100 The linear amount to increment the backoff timer for each retry