On 12/10/2010 2:03 PM, Rob Randall wrote:
> I manged to get my python app past 3GB on a smaller 64 bit machine.
> On a test to check memory usage with gc disabled only an extra 6MB was
> used.
> The figures were 1693MB to 1687MB.
>
> This is great.
>
> Thanks again for the help.
Do remember, tho
I manged to get my python app past 3GB on a smaller 64 bit machine.
On a test to check memory usage with gc disabled only an extra 6MB was used.
The figures were 1693MB to 1687MB.
This is great.
Thanks again for the help.
On 10 December 2010 13:54, Rob Randall wrote:
> You guys are right. If
You guys are right. If I disable the gc it will use all the virtual RAM in
my test.
The application I have been running these tests for is a port of a program
written in a LISP-based tool running on Unix.
It does a mass of stress calculations.
The port has been written using a python-based toolki
On 12/8/2010 10:42 PM, Dennis Lee Bieber wrote:
On Wed, 8 Dec 2010 14:44:30 +, Rob Randall
declaimed the following in gmane.comp.python.general:
I am trying to understand how much memory is available to a 64 bit python
process running under Windows XP 64 bit.
When I run tests just creating
On Thu, 9 Dec 2010 17:18:58 +
Rob Randall wrote:
> Basically the process runs at around 1% and it never seems to grow in size
> again.
> When running the C++ with python app the process slows when a new 'page' is
> required but then goes back to 'full' speed. It does this until basically
> all
I will give it a try with the garbage collector disabled.
On 9 December 2010 17:29, Benjamin Kaplan wrote:
> On Thursday, December 9, 2010, Rob Randall wrote:
> > But the C++ program using up memory does not slow up.
> > It has gone to 40GB without much trouble.
> >
>
> Your C++ program probabl
On Thursday, December 9, 2010, Rob Randall wrote:
> But the C++ program using up memory does not slow up.
> It has gone to 40GB without much trouble.
>
Your C++ program probably doesn't have a garbage collector traversing
the entire allocated memory looking for reference cycles.
> Does anyone ha
On 12/8/2010 11:40 PM, Ian Kelly wrote:
Since a process need not have all its pages in physical memory
simultaneously, there is no reason to suppose that a single process
could not consume the entirety of the available virtual memory (minus
what is used by the operating system) on a 64-bit system
Basically the process runs at around 1% and it never seems to grow in size
again.
When running the C++ with python app the process slows when a new 'page' is
required but then goes back to 'full' speed. It does this until basically
all the virtual memory is used.
I have had memory exceptions when
But the C++ program using up memory does not slow up.
It has gone to 40GB without much trouble.
Does anyone have a 64 bit python application that uses more the 2GB?
On 9 December 2010 16:54, Antoine Pitrou wrote:
> On Wed, 8 Dec 2010 14:44:30 +
> Rob Randall wrote:
> > I am trying to under
On Wed, 8 Dec 2010 14:44:30 +
Rob Randall wrote:
> I am trying to understand how much memory is available to a 64 bit python
> process running under Windows XP 64 bit.
>
> When I run tests just creating a series of large dictionaries containing
> string keys and float values I do not seem to
Rob Randall wrote:
> I am trying to understand how much memory is available to a 64 bit python
> process running under Windows XP 64 bit.
>
> When I run tests just creating a series of large dictionaries containing
> string keys and float values I do not seem to be able to grow the process
> bey
On 01/-10/-28163 02:59 PM, Dennis Lee Bieber wrote:
On Wed, 8 Dec 2010 14:44:30 +, Rob Randall
declaimed the following in gmane.comp.python.general:
I am trying to understand how much memory is available to a 64 bit python
process running under Windows XP 64 bit.
When I run tests just crea
On 12/8/2010 11:42 PM, Dennis Lee Bieber wrote:
The page file can be larger than physical memory because it contains
memory "images" for multiple processes. However, all those "images" have
to map into the physically addressable memory -- so a process is likely
limited to physical memory,
I am trying to understand how much memory is available to a 64 bit python
process running under Windows XP 64 bit.
When I run tests just creating a series of large dictionaries containing
string keys and float values I do not seem to be able to grow the process
beyond the amount of RAM present.
F
15 matches
Mail list logo
