Choosing the Correct Revelation Network Product for Your Network (Network Compatibility,Operating System Compatibility,Performance)

Revelation Software has developed a series of add-on products that provide enhanced performance and reduce network errors for applications using the Revelation Linear Hash filing system. These 'Network Products' are: the Revelation Universal Driver, the Revelation Netware Loadable Module (NLM), and the Revelation Windows 2000 Service.

 

THE NETWORK RULE

In order to ensure the optimal performing environment it is imperative that the proper 'Network Product' is installed. This is based upon which product you use(OpenInsight or Advanced Revelation [version 2.03+])and which network is installed. The rule to use in determining which network product to use is:

 

The Network Rule

 

*Workstations need to be at least Windows NT or above to use the Universal Driver.

**To take advantage of the > 64k capabilities, you will need the Universal Driver

 

 

What are the consequences for not adhering to the "network rule"?

There is nothing that technically enforces the 'network rule'. There are some obvious compatibility issues such as:

The Revelation NLM only works on Novell Netware Networks using IPX

 

The Revelation Windows 2000 Service will only work on Microsoft Windows 2000/NT/2003 Servers

 

It is possible to run without a Network Product, but there are problems that can ensue. When running without a Network Product, users of Advanced Revelation will need to purchase the Revelation Network Performance Pack.

 

THE DIFFERENCE BETWEEN THE REVELATION NPP AND THE REVELATION NETWORK PRODUCTS

 

The only reason customers attempt this configuration is the Revelation NPP costs less than the Universal Driver, Revelation NLM or 2000 Service - don't lose sight that the Revelation NPP does less than the Universal Driver/NLM/Windows 2000 Service and will provide slower performance on loaded(large number of transactions or users) Windows Servers and comparatively significantly slower performance on Novell Netware. We will address each of these points below. Revelation Software does not recommend using the Revelation NPP on a Linux, Novell or Microsoft Windows 2000/NT Server if you have over three users. In this case, you must use the recommended Revelation Network Products to avoid performance degradation. Furthermore, the NPP is not a "cheap" version of the Universal Driver/NLM/Windows 2000 Service. The Revelation Universal Driver, NLM and Windows 2000 Service offer features that the Revelation NPP does not, as outlined in the table below.

 

Feature Differences between the Revelation NPP and the Revelation NLM/NT Service

 

  

PERFORMANCE ISSUES ON LOADED NETWORKS

There are circumstances in which the Revelation NPP may be slower using Microsoft Windows 2000/NT Server or significantly slower using Novell Netware. The locking architecture used by the Revelation NPP is an industry standard method of locking that is termed "Byte Range". This style of locking is implemented in the majority of local area networks - products such as Lantastic, Banyan, Lan Server,and Windows for Workgroups. The definition of 'Byte Range' locking is all locks are funneled through a central file which coordinates multiple workstation access to the data. When a user requests a lock, the central file is opened, and a range of bytes is 'locked'. If a second workstation wants access to the record, it opens the file and checks if the appropriate range of bytes are locked before access is granted. Since all workstation access is granted through a single file, this bottleneck will cause performance to degrade as the number of workstations and/or transactions increases. Due to this architecture, 'Byte Range' lock networks are typically inexpensive,small-scale LAN's handling between one and three users.

 

For larger networks, users often select Novell Netware or Microsoft Windows 2000/NTServer. Instead of using a file based method of locking, these networks use a'semaphore' service consisting of setting lock flags in memory. This method supports many more users, and is optimized for heavy network traffic. The Revelation NLM is created specifically to take advantage of the native Novell services. The NT Service is a 32-bit implementation supporting multiple processors (SMP) written specifically for Microsoft Windows 2000/NT Server.

 

ADVANCED REVELATION AND THE REVELATION NETWORK PRODUCTS

In your existing Advanced Revelation system, you are either running a"Novell" driver or a "Byte Range" driver. (You can determine which your system is running by looking at the 'Network Vendor Type'in the Who screen - Type WHO at TCL). If you have a Novell Network, you will notice you have either the 'Novell Netware" or "AdvancedNetware" driver loaded. If you are running on Microsoft Windows 2000/NTServer or any other network you are running a variation of a "Byte Range" driver.

 

The Novell drivers mentioned above were written and optimized specifically for Novell. If you change the driver to one of the 'Byte Range' drivers, you will notice your performance degrade. This is due to the fact that you are no longer using standard Novell semaphore locking . Similarly, if you replace the Novell driver with the Revelation NPP ("enhanced" Byte Range driver) your performance will also degrade.

 

If your existing Advanced Revelation system is currently using Microsoft Windows 2000/NT Server, you are running a variation of the "Byte Range"driver. In this situation, unlike the above, we are comparing the same locking method (Byte Range vs. Revelation NPP - think of the NPP as "Enhanced Byte Range"). Therefore, if you install the NPP into Advanced Revelation on a Microsoft Windows 2000/NT Server, you should see a slight performance increase assuming you are running a relatively small number of users. This is because the Revelation NPP uses 'Byte Range' locking and is therefore limited by the architecture of this locking method. (Incidentally, the NPP does add some throughput by adding the ability to designate a file in each DOS directory to place the locks). If you have bottleneck issues - either from the amount of transactions or amount of users - you should purchase the Revelation Windows 2000 Service.

 

If you are running Windows 95/NT/2000 workstations, you are required to use the "All Networks" or the Revelation NLM . The 'All Networks' driver and the Revelation NLM both resolve problems introduced with 'Opportunistic Locking' and 'Write-Behind Caching' implemented in Win95/WinNT/Win2000.XP. 

 

In summary, Revelation Software recommends the use of the Revelation NPP on small-scale, low transaction, 'Byte Range' networks. Revelation does not recommend using the Revelation NPP on Novell or NT Networks as comparative performance may degrade, especially when there are over five users. The Revelation NLM and Windows 2000 Service are designed to handle many users and many transactions, providing performance and stability to users of these networks. By following the 'Network Rule,' you will be guaranteed to have the best performing, most reliable system.

    

OPENINSIGHT AND THE REVELATION NETWORK PRODUCTS

The "All Networks" driver is the functional equivalent to the Revelation NPP providing a 'Byte Range' locking method for OpenInsight on small scale systems. The 'All Networks' driver is built into OpenInsight version 3.12 and above. The issues with OpenInsight and the All Networks driver are basically the same outlined above - it is effective for small-scale networks. If you wish to scale your network, the Revelation NLM or Revelation Windows 2000 Service is highly recommended. If you use the "All Networks" Driver with Novell, you will notice a performance slowdown from the Novell Driver also built into OpenInsight, for the same reasons documented above. However, you are required to use the "All Networks" or the Revelation NLM if you are running Windows 95/NT/2000/XP workstations. The 'All Networks'driver and the Revelation NLM both resolve problems introduced with'Opportunistic Locking' and 'Write-Behind Caching' implemented in Win95/WinNT.  For users of Windows 2000/NT Server, the 'All Networks' driver is an appropriate choice for small networks, for larger networks the Windows 2000 Service is highly recommended.Please note that the NPP is part of the Windows 2000 Service and does not need to be purchased separately.

 

Please consult the Network Product Support Matrix to help you determine which network driver is required for a particular network/client/Revelation network product configuration.

 

Updated02/04