|
#1
|
||||
|
||||
|
After almost 2 years of development we are really pleased to make available the V6 beta release for public testing. [Update, 17/Dec/2008: We are out of beta testing and the final V6 release is now available]
This major new release has dozens of new features and 100's of smaller changes. A large proportion of which were implemented as a result of user feedback from the user community. We estimate that there are now over 100,000 web sites and CD's using Zoom Search. We are really proud of this new release, working on it has been like creating a work of art and we sincerely hope you'll enjoy using it as much as we enjoyed creating it. Here is a summary of the major new features,
|
|
#2
|
||||
|
||||
|
More new features:
![]() ... and of course, many other improvements, bug fixes, and performance optimizations than we can fit here.
__________________
Ray Wrensoft |
|
#3
|
||||
|
||||
|
And few more in the latest beta release...
JavaScript capacity increased! A big change is in the JavaScript version, which utilizes a new method to get around a significant limitation in the scripting engine of browsers such as Internet Explorer. This new implementation allows you to index and search a much larger number of files using JavaScript than ever before. We have tested the new version to index upwards of 10,000+ pages and 100,000+ unique words. However, performance varies on Internet Explorer, which is the slowest performing browser (in terms of JavaScript execution). Firefox and Chrome fares much better with such an intensive JavaScript application. PHP and ASP capacity We have also increased the maximum unique words limit for PHP and ASP from 300,000 to 500,000. This was made possible by the optimizations and improvements we have made for these two scripts in V6. Search Statistics PHP Script There is a new script which you can use to generate live statistics on your web server. This script is only available for PHP, and does not generate graphical charts like the "Statistics Report" tool in the Indexer. It will however, provide concise, up-to-date statistics on your server without needing to download the log file. See the Help file for more information (under the "Advanced Options" chapter). Other new improvements include:
__________________
Ray Wrensoft |
|
#4
|
||||
|
||||
|
And one more feature before the final release.
Native 64bit version of the indexer & higher CGI capacity The Zoom indexer will now be available in both native 32bit and 64bit executables. The 32bit software is full compatible with, and could always run on, 64bit versions of Windows. But it was limited to using only 2GB of RAM, regardless of how much RAM was actually installed in the machine. This was a Window 32bit limitation. The native 64bit release of Zoom in V6 allows an almost unlimited amount of RAM to be used, if the RAM is physically available in the machine and you are running a 64bit O/S. There is no functional difference between the 32bit and 64bit releases. They have an identical set of features. The only difference is in how much RAM they can use. Being able to access more RAM, means a higher potential capacity. But as the capacity of the 32bit release was around a million pages, very few people will need to use the 64bit release. So the 64bit release will be made available as part of the Enterprise edition. Removing the RAM bottle neck in the indexer, by itself, doesn't allow for significantly improved capacity however. There were other limits in the CGI script and in the index file format, which was effective 32bit in nature. For example the index had 32bit file pointers and on old versions of Linux it was not possible to handle index files larger than 2GB because of operating system limits. So we have systemically restructured the index file format and it should now support files of around a terabyte in size, at least in theory. (In practice things start to get impractical one you get into 10's of Gigabytes). Long time users might be wondering about the CGI's themselves. Are they also 64bit? The answer is no. The CGI's remain as 32bit executables. They don't use enough RAM to justify making a 64bit release, and the 32bit CGI's remain compatible with 64bit Windows and Linux. So there is no benefit to changing them. So what does this mean for capacity? Capacity in the V4 and V5 releases was effective limited by O/S and file system limits. Now with V6 the limits are related to how much RAM you have installed and how fast your hardware is. Faster hardware allows a larger capacity as large data sets can still be indexed and searched in a reasonable time frame. Over the next few weeks will be posting some benchmarks, but initial testing in house has show search times of a few seconds are still possible with data sets over 2 million pages on a single machine. |
|
#5
|
||||
|
||||
|
V6.0 is now available, 17/Dec/2008.
So this thread can now be closed. But please feel free to open up new V6 threads as issues arise. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|