Subject | Re: Internal gds software ... error |
---|---|
Author | Adam |
Post date | 2006-12-11T10:40:03Z |
--- In firebird-support@yahoogroups.com, "Michael Vilhelmsen"
<Michael.Vilhelmsen@...> wrote:
Windows must be clever enough to use wow64 to run it in 32 bit mode.
As far as the procedure, yes it is as simple as uninstall and
reinstall, just be sure to disable the guardian service if it gets
installed.
Also, if you have manually changed the default firebird.conf cache
sizes, then you will need to choose more suitable values under classic.
If you are up to 1.8GB, then I am confident my guess at 2GB process
limit was correct. I can't see how that can be the case unless you
have a lot of databases and you have really bumped up the cache. Most
people actually get the reverse problem - a mountain of RAM they can't
convince Firebird to use.
Adam
<Michael.Vilhelmsen@...> wrote:
>There is no official 64bit Windows build for 1.5.x or 2.0. I think
>
> More information ...
>
> The server is running Windows 2003 64Bit.
> It has a Dual Core CPU and 4 Gb RAM.
>
> It runs Firebird 1.5.0 SS.
>
>
> The server has been up and running for a month now.
> The problem with clients unable to connect seems to be when Firebird
> has used all of 2 Gb af RAM.
>
> This morning, when noone was connected to the server we saw thar
> Firebird already used 1,8 Gb of RAM.
>
> Tonigth we will restart the server.
> We will then observe to see if the server in time will consume more
> and more memory.
>
> But - Should I upgrade from FB 1.5.0 SS to FB 1.5.3 SS ?
>
>
> If the problem we have can be solved by restarting the server
> periodically thats fine at first.
> Then when FB 2.0 to Windows 64Bit is released we will upgrade there.
>
> Has anyone else experienced anything with FB 1.5 and 64 Bits OS
> (Windows) ?
Windows must be clever enough to use wow64 to run it in 32 bit mode.
As far as the procedure, yes it is as simple as uninstall and
reinstall, just be sure to disable the guardian service if it gets
installed.
Also, if you have manually changed the default firebird.conf cache
sizes, then you will need to choose more suitable values under classic.
If you are up to 1.8GB, then I am confident my guess at 2GB process
limit was correct. I can't see how that can be the case unless you
have a lot of databases and you have really bumped up the cache. Most
people actually get the reverse problem - a mountain of RAM they can't
convince Firebird to use.
Adam