On Thu, Mar 22, 2012 at 10:24 PM, Nikolay Samofatov
nikolay.samofa...@red-soft.biz wrote:
Hello, All!
We completed (conditional) implementation of lock manager buffer 2 GB and
put it into production.
The production system tends to be 100% CPU bound now (as there is a few days
back-log of
Hello, Marius,
Another thing to try is to use a kernel 3.2 if possible
Some of the write locking and scalability issues were solved in kernel 3.2
No, i don't think so. We profiled Linux kernel with Firebird accurately. I have
the entire oprofile
callgraph handy.
The hard bottleneck now
On Fri, Mar 23, 2012 at 9:13 AM, Alex Peshkoff peshk...@mail.ru wrote:
On 03/23/12 00:24, Nikolay Samofatov wrote:
Hello, All!
We completed (conditional) implementation of lock manager buffer 2 GB and
put it into production.
The production system tends to be 100% CPU bound now (as there
23.03.2012 11:13, Alex Peshkoff wrote:
In trunk - definitely. What about 2.5 - not sure. May be having patch
for high-end systems is better approach than commit in svn?
I'd say we need to see the patch before deciding.
Dmitry
