Subject | RE: [firebird-support] Pushing Firebird 2.1 over the edge. |
---|---|
Author | Calin Pirtea |
Post date | 2009-09-25T04:27:24Z |
Hi Alan,
The memory usage is not all that simple because Firebird at the time was running 844 threads which, if Firebird is using 1Mb per thread, means 844Mb that is not reported by task manager on top of existing used memory.
Using 32 bit environment means you cannot have 2000 threads in one single process unless the process changes the way threads are started to use less memory. I am assuming the default is 1Mb of course. Same goes for connections if each connection uses 1 MB.
My question is, when it got into this state should it terminate the best it can? Otherwise it will be left in a non responsive state and no one can use the system until restarted manually.
Cheers,
Calin Pirtea
time. FB memory use was nowhere near a limit (70Mb at the time). So I'm
suspicious of this error reporting what you think it is reporting. And the
server memory was only reporting about 50% of available RAM.
Alan
The memory usage is not all that simple because Firebird at the time was running 844 threads which, if Firebird is using 1Mb per thread, means 844Mb that is not reported by task manager on top of existing used memory.
Using 32 bit environment means you cannot have 2000 threads in one single process unless the process changes the way threads are started to use less memory. I am assuming the default is 1Mb of course. Same goes for connections if each connection uses 1 MB.
My question is, when it got into this state should it terminate the best it can? Otherwise it will be left in a non responsive state and no one can use the system until restarted manually.
Cheers,
Calin Pirtea
> Hi All,I've had this error with 2.1.2 and I was watching the task manager at the
>
> I'm creating a big load of connections to Firebird and during a select
> statement I reached the memory limit for Firebird. The select failed
> with:
> ISC ERROR CODE:335544430
>
> ISC ERROR MESSAGE:
> unable to allocate memory from operating system
time. FB memory use was nowhere near a limit (70Mb at the time). So I'm
suspicious of this error reporting what you think it is reporting. And the
server memory was only reporting about 50% of available RAM.
Alan