This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
admin:features:grids:home [2011/01/31 23:38] deb |
admin:features:grids:home [2016/06/28 22:38] (current) |
||
---|---|---|---|
Line 7: | Line 7: | ||
===== Omnidex Grids ===== | ===== Omnidex Grids ===== | ||
- | **[[admin:features:grids:home|Overview]]** -> [[admin:features:grids:partitions|Partitioning Scheme]] -> [[admin:features:grids:distribution|Distribution Plan]] -> [[admin:features:grids:creation|Grid Creation]] | + | **[[admin:features:grids:home|Overview]]** | [[admin:features:grids:partitions|Partitioning Scheme]] | [[admin:features:grids:distribution|Distribution Plan]] | [[admin:features:grids:creation|Grid Creation]] |
---- | ---- | ||
==== Overview ==== | ==== Overview ==== | ||
Line 15: | Line 15: | ||
An Omnidex Grid consists of one or more computers used in combination to satisfy Omnidex queries. Some Omnidex Grids are placed on one or more large, multi-processor computers. Other Omnidex Grids are placed on an array of inexpensive, commodity, desktop PCs. Both types of grids perform well, and each has distinct advantages. | An Omnidex Grid consists of one or more computers used in combination to satisfy Omnidex queries. Some Omnidex Grids are placed on one or more large, multi-processor computers. Other Omnidex Grids are placed on an array of inexpensive, commodity, desktop PCs. Both types of grids perform well, and each has distinct advantages. | ||
- | An Omnidex Grid always will have a //grid controller// and a collection of //grid nodes//. The grid controller coordinates all activity on the grid and communicates between the user and the underlying //grid nodes//. The //grid nodes// perform all of the work of housing and indexing the data, and fulfilling the queries. The //grid controller// and the //grid nodes// may all be on the same computer, or they may be distributed between multiple //grid servers// as needed for performance and scalability. | + | An Omnidex Grid will always have a //grid controller// and a collection of //grid nodes//. The grid controller coordinates all activity on the grid and communicates between the user and the underlying //grid nodes//. The //grid nodes// perform all of the work of housing and indexing the data, and fulfilling the queries. The //grid controller// and the //grid nodes// may all be on the same computer, or they may be distributed between multiple //grid servers// as needed for performance and scalability. |
Many Omnidex Grids are created as an Omnidex Snapshot, meaning that the underlying data is distributed into flat files across multiple directories or servers. These become very high-performing databases that can satisfy a wide variety of queries very quickly. Omnidex Grids can also be created against the underlying database, though the nodes then remain tethered to the servers hosting the database. | Many Omnidex Grids are created as an Omnidex Snapshot, meaning that the underlying data is distributed into flat files across multiple directories or servers. These become very high-performing databases that can satisfy a wide variety of queries very quickly. Omnidex Grids can also be created against the underlying database, though the nodes then remain tethered to the servers hosting the database. |