Additional Requirements & Recommendations
- – DVD - ROM required for media installation. You do not need this if you have downloaded the installer from the LMKR Support Portal > Downloads page
- – DCOM/Firewalls configured to allow remote access. Only necessary if sharing projects. For DCOM configuration recommendations, refer to the LMKR Support Portal > Knowledge Center > White Papers page
Server performance is subject to a large number of variables. It is impossible to give specific recommendations here, but these are some guiding principles to use. In general, multi-user performance of a GeoGraphix Project Server is best when the server is dedicated to GeoGraphix and not shared with other applications, especially database applications. In addition, consideration should be made for the number of GeoGraphix users and the size and number of concurrently accessed projects. At some point, having multiple project servers becomes a better solution than having all users on one server. Generally, somewhere between 10 and 20 users is when a second server might be suggested.
Networking performance depends on the number of users trying to access a server simultaneously, as well as the bandwidth requirements for those users. Recommendations for server bandwidth typically specify server connectivity at a higher bandwidth than an individual user. For instance, users running at 100 Mbit should be accessing a server running on a 1-Gbit backbone. If users are at 1 Gbit, consider running multiple 1-Gbit connections or a single higher-bandwidth connection on the server.
A large database cache is an important factor to consider when dealing with multiple users accessing large databases. The database engine is capable of addressing a practically unlimited amount of cache memory. The best way to size the memory is to estimate the memory requirements for other running applications and allow the database cache to dynamically allocate any remaining free memory. The engine will only allocate what it needs when using dynamic allocation up to the maximum specified.
It is highly recommended that you let the database engine use as much cache memory as it requires on the host server. Increasing database cache memory is the quickest and most effective way to improve database-related performance on large network projects.
On a workstation, it might be appropriate to reserve 1 to 2 GB for the OS and file system cache and 2 to 4 GB for other running applications. On a dedicated project server, not much memory needs to be reserved for other applications. The ideal maximum varies by the project size, the number of users, and other load considerations. But as a general rule, the higher you can set the maximum, the better.
A great deal of Discovery's access patterns on a server deal with file I/O. Database access, raster images, and seismic data are examples of files that benefit substantially from a fast disk sub-system. Server environments also place a high importance on data integrity and reliability. At a minimum, consider using a RAID 5 (striped with parity) array. As the size of disks increases, you may also want to consider a hot swap drive and/or RAID 6 (striped with dual parity). Using a controller card with its own cache can also help improve performance.
Network Attached Storage (NAS), Storage Area Networks (SAN), and Other Non-Windows Storage Solutions
There are two typical methods used for accessing external storage devices from a project server: iSCSI and CIFS.
- iSCSI allocates a block of storage on the external device and makes it appear to be a physical disk on the project server. This has the advantage of a 100% compliant file system. However, since the external device sees the allocation as one big file, it makes backup and restoration of individual files using the external device's capabilities more difficult. Standard backup and restore procedures from the server will still work.
- Using CIFS for external storage devices depends greatly on the vendor’s implementation of the CIFS protocol used by the Windows platform. In general, a 100% compliant implementation of CIFS for a performant system is required. In particular, the vendor's implementation of the "File Change/Notify" functionality has been problematic. Devices based on the Windows Storage Server should be 100% compatible, since it shares its components with Windows. Implementations based on UNIX/Linux are where problems occur, due to the fact that the kernel level support is not present. Due to these uncertainties with CIFS implementations, LMKR does not technically support CIFS.
This release has several prerequisites that are required to run the software, as well as prerequisites that are used to enhance the software. The prerequisites can be downloaded from the LMKR Support Portal.
Microsoft .NET Framework 3.5
This is specifically required if you are using smartSECTION on a Microsoft Windows® 10 operating system. The Microsoft .NET 3.5 can be downloaded from Microsoft's website and then installed. It is also available in the 3rd Party installers shipped with Discovery 2019.1.
Microsoft .NET Framework 4.5.1
Discovery 2019.1 must have Microsoft's .NET 4.5.1 installed. The Microsoft .NET 4.5.1 can be downloaded from Microsoft's website, and then installed. It is also available in the 3rd Party installer shipped with Discovery 2019.1.
MATLAB Runtime R2018a (9.4)
GVERSE® Field Planner requires MATLAB Runtime R2018a (9.4).
The MATLAB Runtime R2018a (9.4) software can be downloaded from MATLAB's website and then installed. It is also available in the Downloads section of the LMKR Support Portal.
ESRI ArcGIS Runtime Engine
New functionality within GeoAtlas related to geo-referenced images and CAD files requires the ESRI ArcGIS 10 Engine with ESRIArcGIS 10.2.x or 10.3.x or 10.4.x or 10.5.x. ESRI ArcGIS license must be configured by running ArcGIS Administrator with administrative rights, and selecting the ArcGIS Engine Runtime (Single Use) option in the wizard. If the ArcGIS Engine is not installed, a message box will appear but the setup will continue.
Microsoft DirectX 11 End-User Runtimes
Discovery 3D, Pro3D, smartSECTION, GVERSE® Geophysics and GVERSE® Geomodeling require Microsoft's DirectX 11 June 2010 End-User Runtimes to work properly. The Discovery 3D application works only on the Windows 7 (64-bit) or higher operating system. Discovery 3D is not installed unless the computer has Windows 7 (64-bit) or higher. Further Discovery 3D requires a DirectX 11 compatible display card. DirectX 11 June 2010 End-User Runtimes can be installed by downloading the Discovery Third Party Installer.
Platform Update for Windows 7
GVERSE® Geomodeling and GVERSE® Geophysics specifically require Windows platform update package KB2670838 installed on the machine, in case the operating system is Windows 7.
Microsoft Internet Explorer 10 or 11
Microsoft Internet Explorer 10 or 11 must be installed in order to launch GVERSE® NOW.