On 02/10/14 22:31, Kiith-Sa wrote:
If *time* spent by allocations is a problem, profile with `perf top`
(assuming you have Linux): Look for 'gc', 'malloc', 'calloc', etc.
(Plain perf record will also work, but not be as quick/interactive.
CodeXL works too.)
If you have OS X, you can use
On Thursday, 2 October 2014 at 20:16:56 UTC, Gary Willoughby
wrote:
Say i have created a program written in D, what tools are
available for me to track memory allocations?
I wrote a tiny module trackallocs.d that inserts a GC proxy and
outputs to log file (or stdout) all the allocations,
On Friday, 3 October 2014 at 08:18:45 UTC, thedeemon wrote:
On Thursday, 2 October 2014 at 20:16:56 UTC, Gary Willoughby
wrote:
Say i have created a program written in D, what tools are
available for me to track memory allocations?
I wrote a tiny module trackallocs.d that inserts a GC proxy
On Friday, 3 October 2014 at 09:27:50 UTC, Kiith-Sa wrote:
https://bitbucket.org/infognition/dstuff/src/
Mind if I use some parts of it in my profiler? (there's no
license)
Sure, it's in public domain (as noted in readme).
Say i have created a program written in D, what tools are
available for me to track memory allocations?
If you write a program and its performance is slow because you
suspect too many allocations are taking place in unrecognised
areas, what tools or techniques do you use to find where they
On Thursday, 2 October 2014 at 20:16:56 UTC, Gary Willoughby
wrote:
Say i have created a program written in D, what tools are
available for me to track memory allocations?
If you write a program and its performance is slow because you
suspect too many allocations are taking place in
On Thursday, 2 October 2014 at 20:31:29 UTC, Kiith-Sa wrote:
On Thursday, 2 October 2014 at 20:16:56 UTC, Gary Willoughby
wrote:
Say i have created a program written in D, what tools are
available for me to track memory allocations?
If you write a program and its performance is slow because
