jHistorian for Oracle smashes all speed and capacity barriers
The recent release of jHistorian version 2 has meant that the Industrial Software record books need to be updated. Using a modest Pentium III processor with a single CPU and 256 Megabytes, jHistorian managed to store data in the Oracle tables at the staggering rate of 600,000 values a minute. (Plus the additional 600,000 quality bytes.) While this is indeed lightening speed, it was even more noteworthy that the CPU usage only went briefly over the 10 percent figure!

David Fraser the development manager at St James software was rightly pleased with the results. "To our knowledge, this kind of speed is a first for such a modest machine."
How has St James managed to achieve this kind of speed?
"It was ultimately a question of being strategic about the architecture and paying attention to the detail of the coding. At the same time, we had to make certain that our other design constraints were not compromised. For example, we had to maintain our requirement that you can add a tag or a manager without having to restart the historian. This too is kinda unique in our business!"

For the technically minded, have a look at the summary figures below which cover the tests carried out or, if you have the inclination, check out the full benchmarks on our website.

Summary of tests to be put in a table:
Values stored per minute: 1.2million. (600,000 samples and 600,000 quality values.)
Number of tags used: 100,000.
Sample rate used: 6 seconds.
CPU type: 480 MHz, single processor, Pentium III
Ram: 256 Mbytes.
CPU usage: 10%
Hard Drive: Normal IDE with 2.5msec latency.
Operating system: NT with revison 6 service patch
Oracle version: 8i.