On Wed, Jul 16, 2014 at 1:33 PM, Kirk, Benjamin (JSC-EG311)
<benjamin.k...@nasa.gov> wrote:
> On Jul 16, 2014, at 2:25 PM, John Peterson <jwpeter...@gmail.com> wrote:
>
>> The next thing I'll try is re-enabling tbb, but removing the
>> scalable_allocator template parameters from dof_map.h and
>> sparsity_pattern.h, and making sure we're still valgrind-clean.
>> Assuming this works, what is the correct long-term fix?
>> scalable_allocator seems to be an optimization, so the simplest
>> approach is to just remove it...  I wouldn't be opposed to e.g.
>> enabling it only when C++11 is enabled, although that is quite a hack,
>> and only shows that we do not know what the real problem is.
>
> IIRC the scalable allocator is almost a prerequisite to actually see a 
> speedup with TBB here.  Otherwise there's so much per-thread allocation 
> contention things can actually slow down, so I think we need to use it when 
> possible.  Might be worth profiling on a more recent system though rather 
> than relying in my increasingly hazy memory.

Good to know, we should certainly try to keep it in the code!


> Alternatively, does enabling C++11 give us any other allocator we can stick 
> in there?
>
> Also, just found this:
>
> http://valgrind.org/docs/manual/dist.news.html
> looks like bug #317318
>
> 317318  Support for Threading Building Blocks "scalable_malloc"

Oh yeah, forgot about google ... :P  Also found this little hint:

http://kate-editor.org/2013/07/29/intel-threading-building-blocks-scalable-allocator-valgrind/


> should be fixed in valgrind 3.9.0.  What version are you running?

3.7.0, I could try and see if there is a newer binary available for
the system I'm on.

-- 
John

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to