Relatively speaking, rather a lot... there really is no fixed upper limit in terms of rows and columns. The effective upper limit depends on a complex relationship between processor speed, available Windows/Java memory, data types, density of the columns and the number and type of Omniscope views employed in a given file. Omniscope file complexity is principally related to the number of cells (rows x columns), whereas the capacity of the users' computers is most closely related to the amount of RAM in the machine. The best way to determine how Omniscope will perform with larger data sets (over 5 million cells) or very large data sets (over 15 million cells) is to use the free trial.

In general, a recent computer running a 32-bit operating system with:

* 512 MB of RAM should open/navigate files of about 5 million typical cells
* 1.0 GB of RAM should open/navigate files of about 17-18 million typical cells
* 2.0 GB of RAM should open/navigate files up to about 20 million typical cells
* over 2.0 GB of RAM can only be productively utilised on 64-bit platforms

The less than proportional increase between 1.0 and 2.0 GB of RAM results when the 32-bit Windows/Java addressing limit is reached. 64-bit computers with 2.0 GB or more RAM have much higher limits. For more information on Omniscope scaling and performance, and 64-bit operation, consult our KnowledgeBase.

Great to hear

Thank you