I've created repo with initial investigation -
https://github.com/dselivanov/r-malloc/blob/master/README.md. At first
glance it seems jemalloc, tcmalloc, glibc with malloc_trim all work better
than default malloc with glibc. Interesting thing is that glibc with
malloc_trim finishes benchmark a bit
On Saturday, August 12, 2017 5:36:36 PM EDT Dirk Eddelbuettel wrote:
> On 12 August 2017 at 15:10, luke-tier...@uiowa.edu wrote:
> | As the Python posts poitns out, it is possible to use alternate malloc
> | implementations, either rebuilding R to use them or using LD_PRELOAD.
> | On Ubuntu for exa
FWIW if we are talking about alternative allocators, tcmalloc is another
candidate that we are using for our projects where we care about allocations
and performance (another upshot is that it's very flexible so you can do a lot
of cool things if you care). However I didn't try it with R - I'll
On 13 August 2017 at 15:15, Dmitriy Selivanov wrote:
| Very interesting information about switching glibc malloc to jemalloc.
|
| So I see action plan as following:
|
|1. set up some benchmark (need to think about design)
|2. Run it on ubuntu machine with default glibc malloc
|3. Run
Very interesting information about switching glibc malloc to jemalloc.
So I see action plan as following:
1. set up some benchmark (need to think about design)
2. Run it on ubuntu machine with default glibc malloc
3. Run it with malloc_trim passed with reg.finalizer()
4. Run it with j
On 12 August 2017 at 15:10, luke-tier...@uiowa.edu wrote:
| As the Python posts poitns out, it is possible to use alternate malloc
| implementations, either rebuilding R to use them or using LD_PRELOAD.
| On Ubuntu for example, you can have R use jemalloc with
|
| sudo apt-get install libjemalloc
On Sat, 12 Aug 2017, Dmitriy Selivanov wrote:
Strange because in my all my experiments calling malloc.trim always helped
- memory reported by top decreased to the level it supposed to be. Do you
have in mind case when calling malloc.trim won't do anything? Also
shouldn't MALLOC_TRIM_THRESHOLD_ e
Strange because in my all my experiments calling malloc.trim always helped
- memory reported by top decreased to the level it supposed to be. Do you
have in mind case when calling malloc.trim won't do anything? Also
shouldn't MALLOC_TRIM_THRESHOLD_ env variable has impact on malloc.trim
calls? At t
> On Aug 11, 2017, at 12:57 PM, Iñaki Úcar wrote:
>
> 2017-08-11 16:00 GMT+02:00 Martin Maechler :
>>> Dmitriy Selivanov
>>>on Fri, 11 Aug 2017 17:33:31 +0400 writes:
>>
>>> Hi mailing list and R-core. Could someone from R-core please help me to
>>> create account in bugzilla? I wo
2017-08-11 16:00 GMT+02:00 Martin Maechler :
>> Dmitriy Selivanov
>> on Fri, 11 Aug 2017 17:33:31 +0400 writes:
>
> > Hi mailing list and R-core. Could someone from R-core please help me to
> > create account in bugzilla? I would like to submit issue related to
> gc() to
>
Thanks Martin, I've received invitation and will create ticket soon.
Regarding issue - basically the problem is that on operating systems which
use glibc memory is not freed (R releases it, but system doesn't trim it).
Setting corresponding environment variable (MALLOC_TRIM_THRESHOLD_) doesn't
hel
> Dmitriy Selivanov
> on Fri, 11 Aug 2017 17:33:31 +0400 writes:
> Hi mailing list and R-core. Could someone from R-core please help me to
> create account in bugzilla? I would like to submit issue related to gc()
to
> wishlist.
I will create one.
Your previous e-mails
Hi mailing list and R-core. Could someone from R-core please help me to
create account in bugzilla? I would like to submit issue related to gc() to
wishlist.
Related context is here -
https://stat.ethz.ch/pipermail/r-devel/2017-July/074715.html
--
Regards
Dmitriy Selivanov
[[alternativ
13 matches
Mail list logo
