Subject | Re: [firebird-support] Re: after 2.1 to 2.5 migration, nbackup seems to slow operations unusually |
---|---|
Author | unordained |
Post date | 2013-07-11T14:51:17Z |
---------- Original Message -----------
From: Dmitry Yemanov <dimitr@...>
Haven't touched it yet, I can do that this afternoon (gathering data this morning
on how re-upping the lock-hash-slots to 5099, and increasing the lock-memory,
affects things.)
Since we're on Windows Server 2008, the nbackup default would be 'ON', right? And
since we've got the cache-quota set now (default 30% of RAM), I guess the logic
would be that it ought to be safe enough to let nbackup allow the OS filesystem
cache to help it out, rather than brute-force it? Or is there some other logic to
messing with the setting?
I'm not sure why the behavior would have changed from 2.1.5 though, all else being
equal...
Thanks!
-Philip
From: Dmitry Yemanov <dimitr@...>
> Out of curiosity, did you try playing with -D ON/OFF modes for------- End of Original Message -------
> nbackup? If so, does it make any difference?
>
> Dmitry
Haven't touched it yet, I can do that this afternoon (gathering data this morning
on how re-upping the lock-hash-slots to 5099, and increasing the lock-memory,
affects things.)
Since we're on Windows Server 2008, the nbackup default would be 'ON', right? And
since we've got the cache-quota set now (default 30% of RAM), I guess the logic
would be that it ought to be safe enough to let nbackup allow the OS filesystem
cache to help it out, rather than brute-force it? Or is there some other logic to
messing with the setting?
I'm not sure why the behavior would have changed from 2.1.5 though, all else being
equal...
Thanks!
-Philip