TempAlloc: Request for Review For Inclusion in core.memory
Andrej Mitrovic
andrej.mitrovich at gmail.com
Tue Apr 19 07:27:53 PDT 2011
Nice work. I've tried it out with allocating some large float arrays,
quick two test cases were a 94MB and 282MB audio file.
File 1 w/o TempAlloc: 410msecs
File 1 w/ TempAlloc: 184msecs
File 2 w/o TempAlloc 1321 msecs
File 2 w/ TempAlloc 567 msecs
Btw, how much *can* I allocate at once by using new (not specific to
TempAlloc)? I've tried a 500MB file, but allocation fails even though
I have plenty of free memory on my system. Is there a limit to using
'new'?
Of course, ideally I'd use some kind of buffering mechanism where a
portion of a file is loaded into memory, and when that's exhausted I'd
load another chunk. But I'd like to know the limits for a single
memory allocation on the garbage-collected heap. Is there some
internal limit for D? I know I can't allocate more than 3GB in the
entire app, but I'm looking at single allocations.
Pardon me if this all sounds stupid, I'm a complete newb when it comes
to memory allocation mechanics. :)
More information about the Digitalmars-d
mailing list