[graph-tool] shortest_distance / concurrency / graph view
francois.kawala at gmail.com
Mon Oct 10 21:15:27 CEST 2016
Hello thanks for the blazing fast answer! From what I understand, if I
provide a graphView per thread the problem should not occur, is that
Le 10 oct. 2016 19:32, "Tiago de Paula Peixoto" <tiago at skewed.de> a écrit :
> On 10.10.2016 17:28, François wrote:
> > Hello,
> > I suspect the copy_property function not to be thread safe. Remember
> > the issue I observe occurs when I re-use the predecessor map returned
> > by shortest_distance. The copy_property is then called from
> > topology/__init__.py:1441 and the parameter full is None.
> I didn't realize all the workers shared a reference to the same graph.
> Indeed this can be improved. To be honest, thread safety from the python
> side is something that I often do not pay attention to, since it is almost
> never worth it. But please open an issue in the website to make
> copy_property() thread safe, and I will get around to it.
> Tiago de Paula Peixoto <[hidden email]
> graph-tool mailing list
> [hidden email] <http:///user/SendEmail.jtp?type=node&node=4026753&i=1>
> *signature.asc* (817 bytes) Download Attachment
> Tiago de Paula Peixoto <tiago at skewed.de>
> If you reply to this email, your message will be added to the discussion
> To start a new topic under Main discussion list for the graph-tool
> project, email ml-node+s982480n2141189h16 at n3.nabble.com
> To unsubscribe from Main discussion list for the graph-tool project, click
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the graph-tool