if you feel slow downs with database access (inserts) with the new
kernel 3.1 and ext3 Filesystem barriers enabled by default in Ext3
http://kernelnewbies.org/Linux_3.1
Hard disks have a memory buffer were they temporally store the
instructions and data issued from the OS while the disk
On Tuesday 25 October 2011 at 11:12 marius adrian popa wrote:
In other words: if you use Ext3 and you note performance regressions
with this release, try disabling barriers (barriers=0 mount option).
I can understand doing this for routine desktop work. It does make a
difference. But for a
On 10/25/11 13:56, Paul Reeves wrote:
On Tuesday 25 October 2011 at 11:12 marius adrian popa wrote:
In other words: if you use Ext3 and you note performance regressions
with this release, try disabling barriers (barriers=0 mount option).
I can understand doing this for routine desktop work.
On 25/10/2011 07:56, Paul Reeves wrote:
On Tuesday 25 October 2011 at 11:12 marius adrian popa wrote:
In other words: if you use Ext3 and you note performance regressions
with this release, try disabling barriers (barriers=0 mount option).
I can understand doing this for routine desktop work.
On 10/25/11 14:03, Adriano dos Santos Fernandes wrote:
On 25/10/2011 07:56, Paul Reeves wrote:
On Tuesday 25 October 2011 at 11:12 marius adrian popa wrote:
In other words: if you use Ext3 and you note performance regressions
with this release, try disabling barriers (barriers=0 mount
On Tuesday 25 October 2011 at 12:03 Adriano dos Santos Fernandes wrote:
1) FW=ON - each page written by Firebird goes to disk immediately, in
the order issued by Firebird
2) FW=OFF, and use fsync on COMMIT - pages will not be reordered, and
when COMMIT happens they will be written to disk
25.10.2011 14:03, Adriano dos Santos Fernandes wrote:
2) FW=OFF, and use fsync on COMMIT - pages will not be reordered, and
when COMMIT happens they will be written to disk in order
I believe this is wrong assumption. Nobody guarantees that OS will be
flushing the dirty pages from the
25.10.2011 14:03, Adriano dos Santos Fernandes wrote:
2) FW=OFF, and use fsync on COMMIT - pages will not be reordered, and
when COMMIT happens they will be written to disk in order
I believe this is wrong assumption. Nobody guarantees that OS will be
flushing the dirty pages from the
25.10.2011 14:45, Paul Reeves wrote:
The documentation in firebird.conf (v2.5) indicates that this is disabled for
posix.
It's disabled by default (setting = -1). But it does work if reconfigured.
Dmitry
--
The
25.10.2011 14:39, Philippe Makowski wrote:
in fact with theses settings, FW=OFF is safer than before
safe enough to be the default ?
Even in the paranoid mode (MaxUnflushedWrites = 1) they still don't
guarantee the write order. So, if the crash happens while the
transaction is being
Hello, All.
Why CORE-432 was closed with resolution Won't fix? I would like to see
information
about field names in input XSQLDA fields. Should I create duplicate ticket as a
feature
request?
--
SY, SD.
--
11 matches
Mail list logo
