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. It does make a
> difference. But for a database server? The problem is that the old behaviour
> was the wrong behaviour. Letting the hard drive re-order page writes
> completely negates the efforts firebird makes to ensure pages are written in
> the correct order.
Provided that HDD has no capacitor enough to flash cache in case of
power failure. As far as I know they typically have. And FS barriers do
not affect what happens with firebird's blocks - barriers only guarantee
correct order of writes for filesystem data (like superblock).
------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
