Subject | RE: [firebird-support] Pushing Firebird 2.1 over the edge. |
---|---|
Author | Calin Pirtea |
Post date | 2009-09-25T14:29:47Z |
Hi Mark,
I think you missed part of the thread.
If you show VMSize in Task Manager it does _NOT_ show the full VMSize. As per Vlad's reply only when using SysInternals's Process Explorer you can see the real thing.
Just try for yourself with an app using 800 threads.
Calin Pirtea
From: Mark Rotteveel
Helen Borrie wrote:
should be included in the memory figures of taskman, AFAIK. That it
looks like taskmanager is not reporting all memory, is because the
memory column in taskmanager shows the current workingset (ie the
current size of pages paged into physical memory), and not the total
memory usage in virtual memory (to show that you need to add the column
VM size (or maybe assigned size).
--
Mark Rotteveel
I think you missed part of the thread.
If you show VMSize in Task Manager it does _NOT_ show the full VMSize. As per Vlad's reply only when using SysInternals's Process Explorer you can see the real thing.
Just try for yourself with an app using 800 threads.
Calin Pirtea
From: Mark Rotteveel
Helen Borrie wrote:
>> Calin Pirtea wrote:I don't think it does, but if you are talking about total memory: that
>>> 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.
>
> At 03:49 PM 25/09/2009, Dmitry Yemanov wrote:
>
>> FB uses 2MB of stack per thread.
>
> FMI, does Windows ever report stack memory usage per thread? If so, where can it be viewed?
should be included in the memory figures of taskman, AFAIK. That it
looks like taskmanager is not reporting all memory, is because the
memory column in taskmanager shows the current workingset (ie the
current size of pages paged into physical memory), and not the total
memory usage in virtual memory (to show that you need to add the column
VM size (or maybe assigned size).
--
Mark Rotteveel