Threading higher in the stack usually avoids the need for much thread safety for matrices. I can usually us a message passing style to push around updates and avoid the question entirely.
Sent from my iPhone On Apr 19, 2013, at 11:32, Robin Anil <[email protected]> wrote: > Yes, that may be a better approach. Do we in any part of our code share the > vectors across threads? Our Vector implementations are thread-unsafe. Maybe > making it threadsafe or having a threadsafe version maybe one more thing we > can build. > > Robin Anil | Software Engineer | +1 312 869 2602 | Google Inc. > > > On Thu, Apr 18, 2013 at 6:37 PM, Ted Dunning <[email protected]> wrote: > >> On Thu, Apr 18, 2013 at 1:41 PM, Robin Anil <[email protected]> wrote: >> >>> 4) Parallelize operations: Use a consistent sharding function to >> trivially >>> parallelize certain iterative operations across multiple threads. >>> >> >> I have done this with good results, but I find it is usually better to >> thread higher up the stack because coarse threading is often easier than >> fine grain threading. >>
