hanks,
Michael
-Original Message-
From: Oleg Sklyar [mailto:[EMAIL PROTECTED]
Sent: Saturday, May 26, 2007 7:42 AM
To: [EMAIL PROTECTED]
Cc: r-devel@r-project.org
Subject: Re: [Rd] R scripts slowing down after repeated called to compiled
code
I work with images with a lot of processing done i
I work with images with a lot of processing done in C code. Quite often
I allocate memory there up to several gigs in chunks of 10-15 Mb each
plus hundreds of protected dims, names etc. I had a similar problem only
once when due to some erroneous use of an external library, internally
created o
On 25 May 2007 at 19:12, Michael Braun wrote:
| So I'm stuck. Can anyone help?
It sounds like a memory issue. Your memory may just get fragmented. One tool
that may help you find leaks is valgrind -- see the 'R Extensions' manual. I
can also recommend the visualisers like kcachegrind (part of KD
Vladimir:
Thanks for your response. I have done as you requested (with a smaller
dataset--the patterns are still there). Here is the gc()-laden output.
I don;t fully understand the meaning of all parts of these reports. But
it does look like the number of objects grows (and it grows faster on
On Friday 25 May 2007 7:12 pm, Michael Braun wrote:
> Thanks in advance to anyone that might be able to help me with this
>
> Also, it is not just the compiled call that slows down. EVERYTHING
> slows down, even those that consist only of standard R functions. The
> time for each of these functio
Thanks in advance to anyone that might be able to help me with this
problem. I have not been able to find a reference to it in the
documentation on online sources, so I am turning to this group.
I am running R 2.4.1 under Red Hat Enterprise Linux 4, on an x86_64
platform (multi-core Intel Xeon pr
