We connect to two databases. One that stores images and one that stores data. The images database is 4.5 gigs. The data database is 600 mb. There is 16 gigs of memory.

So I am guessing 2.5.2 won't be solving this problem. Still doing the test though, so I will let you know how it goes.

Any other ideas what to look for?

Todd

--- In firebird-support@yahoogroups.com, "Fabiano" <fabianoaspro@...> wrote:
>
> The database is bigger than the RAM memory?
>
> If yes this is an issue of 2.5.1
>
>
>
> You do not need a backup/restore cycle for migrating to 2.5.2
>
> Fabiano
>
>
>
> De: firebird-support@yahoogroups.com
> [mailto:firebird-support@yahoogroups.com] Em nome de todderamaa
> Enviada em: terça-feira, 18 de setembro de 2012 12:22
> Para: firebird-support@yahoogroups.com
> Assunto: [firebird-support] Firebird 2.5.1 to 2.5.2
>
>
>
>
>
> We are having an issue with caching when using Firebird 2.5.1 on a Windows
> Server 2008 box. The system flies when turning forced writes off, but we
> don't want to operate that way.
>
> The strange thing is that we have a number of clients using 2.5.1 on Windows
> Server 2008 and nobody has brought up performance issues.
>
> Anyhow, we were reading about 2.5.2 and how there was a problem with caching
> that was fixed. We are going to try the beta version that is out.
>
> Do we need to backup on 2.5.1 and restore to 2.5.2?
>
> Any help with this issue would be appreciated.
>
> Todd Brasseur
> Compass Municipal Services Inc.
> HOME OF CAMAlot
>
>
>
> _____
>
> Nenhum vírus encontrado nessa mensagem.
> Verificado por AVG - www.avgbrasil.com.br
> Versão: 2012.0.2221 / Banco de dados de vírus: 2437/5275 - Data de
> Lançamento: 09/18/12
>
>
>
> [Non-text portions of this message have been removed]
>