By: Michael S (already5chosen.delete@this.yahoo.com), August 21, 2013 7:15 am
Room: Moderated Discussions
Carlie Coats (coats.delete@this.baronams.com) on August 21, 2013 6:31 am wrote:
> u269b (0xe2.0x9a.0x9b.delete@this.gmail.com) on August 21, 2013 4:12 am wrote:
> [snip...]
> > The model I described does work if the computer has for example
> > 32 GiB physical memory (which is 8x more than the 32-bit address
> > space).
>
> Does *NOT* work if you need a multi-gigabyte stack (as some GIS
> algorithms do),
Do you use the word 'stack' as synonym of LIFO, or for something else?
If the former, then I don't understand how it could be true.
LIFO is one of those structures for which PAE windowing should work very well. Even when, for some reason, you can't map the hot spot into your address space, with LIFO you always can fill/spill into paging pool. For correctly chosen low/high water marks, the overhead of fill/spill process should be very small.
> unless you program the whole thing by yourself
> using disk to emulate the stack, and increasing run-times by
> several orders of magnitude.
>
It's seems, here you are describing the situation in which you were running out physical memory rather than out of address space.
> u269b (0xe2.0x9a.0x9b.delete@this.gmail.com) on August 21, 2013 4:12 am wrote:
> [snip...]
> > The model I described does work if the computer has for example
> > 32 GiB physical memory (which is 8x more than the 32-bit address
> > space).
>
> Does *NOT* work if you need a multi-gigabyte stack (as some GIS
> algorithms do),
Do you use the word 'stack' as synonym of LIFO, or for something else?
If the former, then I don't understand how it could be true.
LIFO is one of those structures for which PAE windowing should work very well. Even when, for some reason, you can't map the hot spot into your address space, with LIFO you always can fill/spill into paging pool. For correctly chosen low/high water marks, the overhead of fill/spill process should be very small.
> unless you program the whole thing by yourself
> using disk to emulate the stack, and increasing run-times by
> several orders of magnitude.
>
It's seems, here you are describing the situation in which you were running out physical memory rather than out of address space.