| Subject | One Transaction can PEG XEON cpu @ 100% starving others |
|---|---|
| Author | Larry Hengen |
| Post date | 2005-01-25T15:48:29Z |
Our application pegs the Firebird XEON CPU at 100% under high load,
rendering the application unresponsive. Is it possible to:
a) run multiple instances of Firebird on the same machine on a
seperate CPU
b) have both instances updating the same database file. What are the
contention/corruption issues?
c) how can we prevent one database connection from monopolizing
Firebird. One transaction from a single connection can peg Firebird
's CPU utilization at 100% causing other connections to be starved to
the point they are dropped, and new ones are denied.
rendering the application unresponsive. Is it possible to:
a) run multiple instances of Firebird on the same machine on a
seperate CPU
b) have both instances updating the same database file. What are the
contention/corruption issues?
c) how can we prevent one database connection from monopolizing
Firebird. One transaction from a single connection can peg Firebird
's CPU utilization at 100% causing other connections to be starved to
the point they are dropped, and new ones are denied.