Thank you very much for the advice, Hannes.
I did not think of this too well. But of course this sounds very
logical. I will re-configure the server to match the most popular
database page size (I have 6 different databases).
I will first consult different papers I have from
03.01.2015 03:08, André Knappstein wrote:
I created a test table on both old and new server to play with updates
and inserts (~ 150.000 records)
Performance with 2.5.3 x64 on Win2008 is constantly
changing, but at best its some 8 seconds and worst even 2 minutes!
Performance with
Thank you Dmitry.
Seems I found the solution to the real problem parallel to your
posting of the message (BBU failure report resetting cache parameters).
The difference on old hardware (2.9 - 3.2) seconds probably is due to
inaccuracy in the very simple test methods. And, yes,
Operations (new Server)
Read : 2.247
Writes : 5.960
Fetches: 2.476.240
Marks : 807.922
Operations (old Server)
Read : 8.516
Writes : 6.084
Fetches: 1.602.243
Marks : 582.584
Guten Tag André Knappstein knappst...@beta-eigenheim.de [firebird-support],
am Samstag, 3. Januar 2015 um 10:45 schrieben Sie:
Stripe size is 64K, btw.
much too big , best size for a stripset ist same as DB Page Size
Strip Set 64Kb means that the controller will read and write Blocks of
Hello Vlad,
It is sure Raid 0 with 3 * 600 GB Toshiba SAS. I only installed the
server today. I did not use the LSI Raid BIOS for configuration but
the server view installation kit from the producer. So I will have
to look up stripe size and BBU status.
Next week I will also apply a
Hi, André !
[Old]
Server 2003 x86 no service packs
Xeon with 4 GB RAM
Classic 1.5.4 (x86, of course)
Raid 0 on 2 * 500 GB SAS (though this is from memory, I should look it up...)
[new]
Server 2008 R2 x64 SP1
Xeon with 8 GB RAM (I will shortly add +8)
Classic 2.5.3 x64
Raid 0 on 3 *
