Subject | Re: Question to entry in log file |
---|---|
Author | Michael Vilhelmsen |
Post date | 2008-05-14T12:59:31Z |
>Agreed ;-)
> That can't be good.
>Its happening some 1 - 3 times a week.
> 2GB is the maximum addressable memory of a single 32 bit process. The
> amount of memory required by Firebird is a surprisingly complex
> calculation, including the page sizes of the different databases as
> well as the cache sizes (measured in pages) etc.
>
> If hitting 2GB is not just a 'one off', then you need to do something
> about reducing your cache or something like that.
>I have looked into the CS model.
> Another option (and the path we went down) is to use Classic Server.
> Classic server allocates a process to each connection which has two
> benefits for you.
>
> 1. The 2GB limit is now 2GB per connection (which would require a
> massive cache setting to worry about).
>
> 2. If the engine does encounter an unexpected condition which causes a
> crash, it is only the single connection that is impacted.
It can be used, but require some changes in our program.
It can be done, but we really dont have the time/money to do this.
Basically I was just asking if this error indeed is a result of
running out of memory.
And if it is I have some solutions.
1.
Live with
2.
Wait until FB will be fixed.
Sinse I cant reproduce it, I cant give a "working error" senario.
3.
Switch to CS.
4.
Or - Switch to FB 2.1 64 Bit.
This is the action we have taken.
We are about to convert them all to FB 2.1.
But its not done in a day.
Michael