546
edits
Performance Optimization Guide: Difference between revisions
→Database queues
No edit summary |
|||
| Line 90: | Line 90: | ||
== Database queues == | == Database queues == | ||
The database mode is an extension for large Allegro models with | The database mode is an extension for large Allegro models with multiple CPU sockets and it is disabled by default. This mode is only recommended for Allegro 3500 rev1 and Allegro 5500 rev1. It helps improving very high database loads (millions of open connections and new connections) over multiple CPUs. See [[DB mode]] for more details. | ||
If enabled, you can check if there are message drops between the analyzer threads and the DB threads in the load statistics. | If enabled, you can check if there are message drops between the analyzer threads and the DB threads in the load statistics. | ||
The ratio of DB threads vs analyzer threads can be adjusted so that ideally all threads have similar load. | |||
The advantage of the DB mode is that additional message queues are used which can buffer much more information and therefore reduce the load on the analyzer threads. This will reduce the likelihood of skipped packets. | |||
== Disk I/O queues == | == Disk I/O queues == | ||