GH_Structure thread safety

Hello all,

is <GH_Structure> thread-safe? Has anyone ever tried populating a GH_Structure with data from multiple threads?

I. e. is it similar to Net 4's ConcurrentDictionary? Or will it fail when multiple threads try to store data at the same time?

Not a big issue, I can bypass it by locking it upon access or by using a ConcurrentDictionary and turning it into a GH_Structure only upon passing data back to GH, but I though I'd ask out of curiousity...

Cheers,

Dan

P.S.: A very quick test returned some KeyNotFound Exceptions

Replies to This Discussion

Permalink Reply by David Rutten on March 27, 2015 at 8:06am

No. Practically nothing is thread-safe in GH1.

Permalink Reply by David Rutten on March 27, 2015 at 8:14am

And there are no plans to make the GH_Structure<T> equivalent in GH2 threadsafe either. The problem is that the items within branches are ordered, and if you are writing items to branches from multiple threads then the ordering is basically up for grabs.

It would be possible to make several tree methods threadsafe, but of course that comes at a performance cost. I think it'll be more likely that I'll provide a thread-safe tree factory class that can be used in those rare cases where it's needed.

Permalink Reply by Daniel Gebreiter on March 27, 2015 at 8:19am

ok cool. As I mentioned I can work around the issue without problem by having a little class to convert ConcurrentDictionaries into GH_Structure before passing data back to GH.

Thanks!

RSS