Hello Kjell,

>Is your page cache large enough? I'd recommend superclassic to be able

to utilize a very large page cache, e.g. 20 Gbyte, that's shared for all
connections.

>Classic has separate page cache per connection so cache can't be too

large, and superserver has problems with multiple cpu:s/cores.

It's not true - SuperClassic has no real shared cache. Consider it as
Classic which is put into the single process.
Also, setting big cache is not a panacea at all and even not the best
solution for all cases, and in most cases database file is cached well
enough by operation system.

Look at the presentation for "Firebird Performance testing webinar", slide 7
http://www.slideshare.net/mindthebird/firebirdperformancetesting

Regards,
Alexey Kovyazin
IBSurgeon