search for: spam_bayes

...en. We happen to generate an ungodly amount of code, which we're trying to reduce. However, this means that LLVM allocates a lot of memory for us, and it grows our heap by several MB over what it would normally be. The breakdown was roughly 8 MB gets allocated for this one compilation in the spam_bayes benchmark, with 2 MB coming form register allocation and 2 MB from SDNodes. We are looking at using mmap/munmap to avoid permanently growing the heap. This patch switches all allocators over to mmap, so you can see a lot of "stitches" in the graphs, where an allocator is created and thr...

...nerate an ungodly amount of > code, which we're trying to reduce. However, this means that LLVM > allocates a lot of memory for us, and it grows our heap by several MB > over what it would normally be. The breakdown was roughly 8 MB gets > allocated for this one compilation in the spam_bayes benchmark, with 2 > MB coming form register allocation and 2 MB from SDNodes. > > We are looking at using mmap/munmap to avoid permanently growing the heap. Don't try to outsmart malloc, you are going to lose ;-) This all depends on specific kernel implementation details, but you ri...

On Aug 7, 2010, at 7:05 PM, Steven Noonan wrote: > I've been doing work on memory reduction in Unladen Swallow, and > during testing, LiveRanges seemed to be consuming one of the largest > chunks of memory. That's interesting. How did you measure this? I'd love to see your data. Note that the LiveRange struct is allocated by a plain std::vector, and your patch doesn't

...ount of code, which we're trying to reduce. However, > > this means that LLVM allocates a lot of memory for us, and it grows > > our heap by several MB over what it would normally be. The > > breakdown was roughly 8 MB gets allocated for this one compilation > > in the spam_bayes benchmark, with 2 MB coming form register > > allocation and 2 MB from SDNodes. > > > > We are looking at using mmap/munmap to avoid permanently growing > > the heap. > > Don't try to outsmart malloc, you are going to lose ;-) > > This all depends on speci...

...nerate an ungodly amount of > code, which we're trying to reduce. However, this means that LLVM > allocates a lot of memory for us, and it grows our heap by several MB > over what it would normally be. The breakdown was roughly 8 MB gets > allocated for this one compilation in the spam_bayes benchmark, with 2 > MB coming form register allocation and 2 MB from SDNodes. > > We are looking at using mmap/munmap to avoid permanently growing the heap. > > This patch switches all allocators over to mmap, so you can see a lot > of "stitches" in the graphs, where an...

Hi folks, I've been doing work on memory reduction in Unladen Swallow, and during testing, LiveRanges seemed to be consuming one of the largest chunks of memory. I wrote a replacement allocator for use by BumpPtrAllocator which uses mmap()/munmap() in place of malloc()/free(). It has worked flawlessly in testing, and reduces memory usage quite nicely in Unladen Swallow. The code is available