dotnetrdf-develop Mailing List for dotNetRDF (Page 10)

Brought to you by: kal_ahmed, rvesse

dotnetrdf-develop — Developer Discussion and Feature Request

You can subscribe to this list here.

2009	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug (1)	Sep	Oct (1)	Nov	Dec
2010	Jan	Feb (11)	Mar (17)	Apr (12)	May (2)	Jun (20)	Jul (2)	Aug (2)	Sep (2)	Oct (2)	Nov	Dec (5)
2011	Jan (4)	Feb (1)	Mar (2)	Apr (2)	May (5)	Jun	Jul (12)	Aug (4)	Sep (5)	Oct (1)	Nov (38)	Dec (27)
2012	Jan (46)	Feb (182)	Mar (83)	Apr (22)	May (68)	Jun (47)	Jul (135)	Aug (84)	Sep (57)	Oct (45)	Nov (27)	Dec (61)
2013	Jan (59)	Feb (78)	Mar (66)	Apr (107)	May (27)	Jun (56)	Jul (53)	Aug (3)	Sep (19)	Oct (41)	Nov (44)	Dec (54)
2014	Jan (49)	Feb (72)	Mar (22)	Apr (41)	May (63)	Jun (27)	Jul (45)	Aug (12)	Sep (3)	Oct (8)	Nov (27)	Dec (16)
2015	Jan (3)	Feb (20)	Mar (6)	Apr (4)	May (15)	Jun (2)	Jul (4)	Aug	Sep (1)	Oct (1)	Nov	Dec
2016	Jan	Feb	Mar	Apr (16)	May (9)	Jun (1)	Jul	Aug	Sep	Oct	Nov	Dec

Flat | Threaded

<< < 1 .. 8 9 10 11 12 .. 83 > >> (Page 10 of 83)

[dotNetRDF-Develop] Issue CORE-418 has been added to a project you are monitoring.

From: <tr...@do...> - 2014-05-27 16:33:48

<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>Investigate whether GRAPH clause evaluation can be safely parallelised with PLINQ</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>Milestone:</b></td>
    <td>1.0.6</td>
  </tr>
  <tr>
    <td><b>Category:</b></td>
    <td>Query</td>
  </tr>
  <tr>
    <td><b>Priority:</b></td>
    <td>Normal</td>
  </tr>
  <tr>
    <td><b>Type:</b></td>
    <td>Improvement</td>
  </tr>
  <tr>
    <td><b>Description:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	One thing noted in investigation of CORE-416 was that GRAPH clause evaluation is not currently parallelised. &nbsp;For clauses that work over large numbers of graphs and have complex inner algebras this means their evaluation can be rather slow. &nbsp;Since the management of the active graph is already implemented so as to be thread safe it should in principal be possible to parallelise the evaluation of GRAPH clauses to improve performance while retaining correctness.</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=418" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=418</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>

[dotNetRDF-Develop] Issue CORE-417 has been updated by Rob Vesse

From: <tr...@do...> - 2014-05-27 16:30:54

<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>Rewrite ExplainQueryProcessor to use event based explanations</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Core Library (dotNetRDF.dll)</td>
  </tr>
  <tr>
    <td colspan="2"><b>Changes:</b></td>
  </tr>
  <tr>
    <td colspan="2">
      <ul>
        <li>Related issue changed from "" to "Added"
                                </li>
      </ul>
    </td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=417" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=417</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>

[dotNetRDF-Develop] Issue CORE-417 has been added to a project you are monitoring.

From: <tr...@do...> - 2014-05-27 16:28:15

<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>Rewrite ExplainQueryProcessor to use event based explanations</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>Milestone:</b></td>
    <td>Unscheduled</td>
  </tr>
  <tr>
    <td><b>Category:</b></td>
    <td>Query</td>
  </tr>
  <tr>
    <td><b>Priority:</b></td>
    <td>Low</td>
  </tr>
  <tr>
    <td><b>Type:</b></td>
    <td>Refactor</td>
  </tr>
  <tr>
    <td><b>Description:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	Currently the ExplainQueryProcessor produces explanations only as textual output to Console.Out, Console.Error, Debug and/or Trace depending on configuration. &nbsp;This issue proposes divorcing the output presentation from the processor by using events. &nbsp;Essentially explanations would be issued via events which users could then present however they wished. &nbsp;The amount of events produced would still be controlled by the ExplanationLevel but it would be refactored to remove flags specifically relating to how things are output. &nbsp;This would have the side effect of making the ExplanationLevel enumeration much simpler. &nbsp;It would also make it much easier to test the explain query processor and to wire it up usefully into GUIs</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=417" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=417</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>