On Thu, Mar 22, 2012 at 10:24 PM, 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 is a few days
> back-log of work).
> All 24 cores
On 04/05/12 21:01, Carlos H. Cantu wrote:
> Why do not start with a simpler solution?
>
> Encryption could be enabled only in two moments:
>
> 1) When creating database
> 2) When restoring a backup
>
> PS: I'm sure some people (specially the ones running 24x7) will complain
> about this suggestion
On 04/06/12 00:46, Ann Harrison wrote:
> On Mon, Mar 5, 2012 at 6:25 PM, Claudio Valderrama C.
> wrote:
>
>> (Thorny issue, I hope Ann Harrison will comment.)
>>
>>
> And now, finally, a month later she does. Included after my signature is a
> bit of MySQL code which may explain my desire to ke
AP> This looks like half-done thing for me.
Sure, the suggestion was just to not delay the release of FB 3 more than
it is already delayed. But if you think a more complete solution could
be done "in time", of course it would be the ideal thing ;)
[]s
Carlos
http://www.firebirdnews.org
FireBase -
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 bottlene
