23 May
2012
23 May
'12
2:35 p.m.
Hi everyone,
I'm working on a reasonably large piece of Python software which uses
PyCUDA for the performance-critical section of the code. I've been
experiencing a memory leak, and while trying to track it down I've
noticed that PyCUDA has a large virtual memory footprint -- somewhere in
the ballpark of 36GB even when no arrays have yet been allocated. Is
this typical for PyCUDA, or is there perhaps something wrong with my
setup?
Thanks,
'
Brendan Wood
23 May
23 May
4:01 p.m.
This is not specific to pycuda, but to cuda itself. It is a new
feature (~unified addresse space) that they have that request this. I
don't know how to disable this feature as I don't use it.
Fred
On Wed, May 23, 2012 at 10:35 AM, <wood(a)synchroverge.com> wrote:
Hi everyone,
I'm working on a reasonably large piece of Python software which uses PyCUDA
for the performance-critical section of the code. I've been experiencing a
memory leak, and while trying to track it down I've noticed that PyCUDA has
a large virtual memory footprint -- somewhere in the ballpark of 36GB even
when no arrays have yet been allocated. Is this typical for PyCUDA, or is
there perhaps something wrong with my setup?
Thanks,
'
Brendan Wood
_______________________________________________
PyCUDA mailing list
PyCUDA(a)tiker.net
http://lists.tiker.net/listinfo/pycuda
3210
days inactive
3210
days old
1 comments
2 participants
participants (2)
-
Frédéric Bastien -
wood＠synchroverge.com