The TCL (The Command Line) window is an invaluable part of OpenInsight, but at times it can feel restrictive or wanting for more features. This blog article demonstrates how Windows PowerShell can be a flexible enhancement for the command line window with a minimal learning curve while making the task of querying OpenInsight data a lot easier.
To install the Universal Driver 5, Revelation Software provides a temporary installation key for use during the installation process. This is different from previous versions of the Universal Driver where a static serial number was needed during installation. While the Universal Driver 5 installation key’s expiration date is sufficient for most projects (and can be extended upon request) you may find yourself in the situation of having an expired installation key after hours but need to migrate to a new server. While installing from the setup file is the preferred installation method you can manually copy the Universal Driver 5 to a new server following these steps.
The standard multi-user deployment practice for OpenInsight involves executing OINSIGHT.exe across the network from a shared network folder. By default Windows distrusts network folder locations that haven’t been previously trusted and can’t be detected as part of the local intranet. This results in Windows displaying the Open File – Security Warning before launching the program.
In this article we’ll cover 3 methods to prevent the Open File – Security Warning by configuring Windows to trust the shared OpenInsight network location.
The rule of thumb when it comes to the Universal Driver’s LinearHash service and server performance is to have enough free physical RAM available on the server to fit all the commonly accessed OpenInsight database files (the LK and OV files managed by the LinearHash service) into memory. This article walks through the problems associated when requests for commonly accessed LinearHash files exceed the amount of available server memory.
This is a continuation of our series focusing on the performance difference of the Universal Driver 5 and 4.7. In what is likely to be the last article in the series, we resume testing the number of simultaneous clients and the rate in which they are able to read records from the Linear Hash service. Please note, however, that these tests were performed with UD 188.8.131.52. Since then, Revelation Software has released two more patches. The latest patch addresses some rather significant performance issues which were identified in the wild. Given that our tests are synthetic, we do not expect the following results to vary much. Therefore we opted not to retest our results in the latest release. Continue reading
The previous articles in this blog series focused on the performance differences between the UD 5 and 4.7 by running tests directly on the server where the Linear Hash service was installed. This essentially limited our tests to single client loops that didn’t have the latency introduced by the network.
In this article the tests will focus on running OpenInsight across the network in parallel from 5 servers running multiple copies of the test program.
In this blog series, the UD 5 Performance Part 1 article focused on benchmarks between the UD 4.7 and UD 5.0 using a simple read / modify / write loop running directly on the server. This article continues the same series of testing by including record locking in the test loop to compare the impact of locking between both Universal Drivers. Details about the test setup and testing environment are included in part 1, and since this is a continuation we will not review the details in this part.
Since writing part 1, Revelation Software also released an article on UD 5 and UD 4.7 Benchmarks. Their benchmarks compared the overall test time where as our series is more focused on throughput (records read/written per second). Two key differences between the Revelation tests and the testing methodology in our series is the Revelation Software benchmarks include locking and wrote new records into a new table. This series does not write any new records but instead modifies only existing records.