This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:applications:production [2009/12/08 18:00] els |
admin:applications:production [2012/10/26 14:26] (current) |
||
|---|---|---|---|
| Line 31: | Line 31: | ||
| ==== Load Balancing ==== | ==== Load Balancing ==== | ||
| - | Omnidex responds well to load balancing. Omnidex does not provide its own load balancing, but rather responds to general load balancers that are used across the application or the enterprise. Typically, load balancers direct queries to lightly loaded servers, and this helps insure that all Omnidex queries remain fast. Some load balancers may also direct certain classes of queries to specific servers in recognition of their resource needs. | + | Omnidex responds well to load balancing. Omnidex does not provide its own load balancing, but it easily responds to general load balancers that are used across the application or the enterprise. Typically, load balancers direct queries to lightly loaded servers, and this helps insure that all Omnidex queries remain fast. Some load balancers may also direct certain classes of queries to specific servers in recognition of their resource needs. |
| ==== Connection Pools ==== | ==== Connection Pools ==== | ||
| - | Connection pools are a common way to insure the speed of queries by maintaining a set of cached connections. These cached connections keep the Omnidex Environment open, along with the corresponding database connections and Omnidex index files. Applications can use connection pooling services such as Java's DBCP services. Alternatively, Omnidex Network Services provides a connection pooling facility. | + | Connection pools are a common method of caching database connections. This helps insure the speed of queries. These connection pools will the Omnidex Environment open, along with the corresponding database connections and Omnidex index files. Many applications use connection pooling services such as Java's DBCP services. Alternatively, Omnidex Network Services provides a connection pooling facility. |
| ==== Competing Applications ==== | ==== Competing Applications ==== | ||
| - | Omnidex performance can be impacted by other applications running on the server. One of the most common examples of this is the relational database itself. Most relational databases will vary number of concurrent processes and the amount of memory to maximize their performance. Relational databases rely more heavily on disk access as well. It is common to see a large multi-processor machine with plenty of memory and fast disk drives fully consumed by the relational database. When this happens it is appropriate to move Omnidex onto a different server than the database. | + | Omnidex performance can be impacted by other applications running on the server. One of the most common examples is the relational database itself. Most relational databases will spawn as many threads as the server will support, and will consume the majority of the memory on the server. This maximizes their performance but degrades the other processes on that server. Relational databases rely more heavily on disk access as well. It is common to see a large multi-processor machine with plenty of memory and fast disk drives fully consumed by the relational database. When this happens it is appropriate to move Omnidex onto a different server than the database, and direct Omnidex to access the database over the network. |
| ==== Periodic maintenance ==== | ==== Periodic maintenance ==== | ||
| - | Omnidex applications do not need much periodic maintenance. Primarily, it is valuable to insure that the Omnidex index files are unfragmented by regularly defragmenting the disk drives. This is also important for the underlying data, especially in the case of raw data files. Omnidex will also use temporary file space, and this drive should be maintained with plenty of unfragmented disk space. | + | Omnidex applications do not need much periodic maintenance. It is valuable to defragment the Omnidex index files by regularly defragmenting the disk drives. It is also important to defragement the underlying data, especially in the case of raw data files. Omnidex uses a temporary file space, so so the drive containing the temporary file space directory should be maintained with plenty of unfragmented disk space. |
| ====== ====== | ====== ====== | ||