MudShark on an Azure Server
MudShark was designed and developed primarily for a conventional computer or network environment, where the software is installed and run on the local computer. Although we have not tested an Azure Server set up, some customers have had success installing MudShark on a Terminal Server. For an Azure set up, a Floating licence is required.
1. Are there any requirements for using MudShark for an Azure Server?
An Azure Server setup would require a Floating licence of MudShark or MudShark + Trench.
2. Are there any computer recommendations to handle the GPU workloads?
MudShark is based on full 3D graphics manipulation, so we find many customer have more than 2GB ram (we have found most graphics cards you can buy now have more ram than that). So, dependant on how many simultaneous users will connect at once,the more users will require a more powerful graphics card.
3. Are there any computer recommendations to handle the CPU workloads and ram?
Calculating in MudShark is compute and ram intensive. Depending on the complexity of the project, it can take between a few seconds and half an hour to calculate a project; this will use varying amounts of ram and CPU. The server will need enough capacity to carry out the calculation, without slowing down other users. If multiple users are calculating a project, this will also need to be taken into consideration for computing power.
4. How is data managed by MudShark?
MudShark stores project files in a shared folder and the SQL Server stores nominal information about the projects, and global information. The shared directory and sql server can be on any server, or on different servers from each other as long as the users have access to them through the network.
5. What access or technology is required to access a centralized setup from different respective clients and services?
A floating licence is required for each active user. All users will require internet access for the acquisition and release of a user licence. All users will need to have access to the shared data folder and to be able to connect to the SQL Server instance on the network.