July 25th, 2011, 09:21 PM
Windows Server 2008 r2 putting FB 2.0 database into RAM
I recently deployed a production enviroment after many weeks of testing in the lab, but after going live, the server unexpectedly chews up RAM like crazy, although not consistently.
I have two identical VM's running windows server 2008 r2. I use ibreplicator to replicate the changes from machine 1 to machine 2. restarting Firebird will resolve the issue for 12 to 24 hours or so.
this doesnt happen on the secondary server, or the old production server (same version of FB, same config file, different OS - server 2003 sbs)
Checking the ram usage with RAMMAP shows that the database is being placed into RAM
I cant attach/link an image of it, so you will just have to imagine a list of files in ram with a FDB file taking 80% of the total ram or try putting appropriate URL stuff infront of