From: <tr...@do...> - 2013-04-12 18:33:47
|
<p>A new comment has been added to the following issue.</p> <table border="0"> <tr> <td width="90px" valign="top"><b>Title:</b></td> <td>Generating Graph diff report causes memory usage explosion for isomorphic graphs with lots of blank nodes</td> </tr> <tr> <td><b>Project:</b></td> <td>Core Library (dotNetRDF.dll)</td> </tr> <tr> <td><b>Created By:</b></td> <td>Rob Vesse</td> </tr> <tr> <td><b>Date:</b></td> <td>2013-04-12 07:32 PM</td> </tr> <tr> <td><b>Comment:</b></td> </tr> <tr> <td colspan="2"><p> I believe the issue should now be resolved, I identified and fixed two things.</p> <ol> <li> The code for GenerateMappings() was flawed and would get stuck spinning and eating memory indefinitely. I rewrote from scratch so that I could use yield return which makes the code much faster and should now be correct (though I am not 100% certain on this)</li> <li> I also added an intermediate mapping step between rules based and brute force mappings which takes a divide and conquer approach. It splits the unmapped blank nodes into their isolated sub-graphs and then attempts to map each one independently, this makes the possible solution space much smaller and results in a much more efficient, accurate and effective mapping algorithm.</li> </ol> <p> Leaving at 95% as Tom has additional test cases to add</p></td> </tr> </table> <p> More information on this issue can be found at <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=345" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=345</a></p> <p style="text-align:center;font-size:8pt;padding:5px;"> If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options. </p> |