R: [firebird-support] How to improve Firebird 2.5.3 Disk I/O on Windows server 2012 R2

2014-09-27 Thread 'Costantino Molinari' c.molin...@tiscali.it [firebird-support]
Hi Sean, thanks for the contribution. Some answers to your requests: 1) Logic of application. It is a Microfocus Cobol legacy application, with latest (2014) x64 runtime. The long time is obviously not relative to a simple sql command, but to the overall execution. We have developed a

Re: R: [firebird-support] How to improve Firebird 2.5.3 Disk I/O on Windows server 2012 R2

2014-09-27 Thread Doychin Bondzhev doyc...@dsoft-bg.com [firebird-support]
Hi Costantino, I did some experimenting before one year and I found that Firebird is much faster when you use page size = cluster size on the file system. So if your file system is with 4K cluster I suggest to use page size of 4K. This is very helpful when you have Forced Write = ON.

Re: R: [firebird-support] How to improve Firebird 2.5.3 Disk I/O on Windows server 2012 R2

2014-09-27 Thread fabianoas...@gmail.com [firebird-support]
Do not change to a SSD! Corruption will occur. Em 27/09/2014 11:16, Doychin Bondzhev doyc...@dsoft-bg.com [firebird-support] firebird-support@yahoogroups.com escreveu: Hi Costantino, I did some experimenting before one year and I found that Firebird is much faster when you use page size =

[firebird-support] page type N lock denied(216) or lock conversion denied(215)

2014-09-27 Thread abad...@tut.by [firebird-support]
Is bug http://tracker.firebirdsql.org/browse/CORE-2848 http://tracker.firebirdsql.org/browse/CORE-2848 fixed in FB 2.5.3? We have had this bug in two FB 2.5.2 classic server installs and it still appears sometimes after updating to 2.5.3. Page number in error message indicates that page

Odp: [firebird-support] How to improve Firebird 2.5.3 Disk I/O on Windows server 2012 R2

2014-09-27 Thread 'liviusliv...@poczta.onet.pl' liviusliv...@poczta.onet.pl [firebird-support]
Hi, If you use default fb config then i suppose your cache settings is very very small. Change DefaultDbCachePages to value greater then your db size in pages. Then restart server and run test again. You should have fastest response time. I recommend you also 16k db page size for better index