[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tsf-dev] TSF process feedback, part 1: statement graphs and references
|
Hey Derek,
Thanks for the reply.
On 22/04/2026 14:33, Derek M Jones via tsf-dev wrote:
Another gotcha: our graph of statements has become simply too big,
and has too many different owners.
Limiting the size will limit it's applicability.
Some form of modularization is needed.
Indeed. This is what the Remote Graphs feature is aiming for. I haven't
been able to use it yet myself, I'd be very interested to see an example
of this being used somewhere.
https://pages.eclipse.dev/eclipse/tsf/tsf/tools/remote-graph.html
There is an issue open with more work planned here:
https://gitlab.eclipse.org/eclipse/tsf/tsf/-/issues/514
References have another cost, due to the "Suspect item" and "Suspect
link" detection that flags when they change. I'll discuss this below in
the "Modifying the statements" section.
Lesson: keep references to the minimum necessary, and review them
carefully.
Surely it's better to have the references? Not having them is
worse than having too many.
Like I said, there is a cost. Trudag has to fetch each reference each
time you run it. And, each reference is monitored for changes and
affects the "Suspect" state of the statement. So too many references
will slow you down.
There are a couple of open issues I've spotted about classifying
different types of reference, which might help...
https://gitlab.eclipse.org/eclipse/tsf/tsf/-/issues/320
https://gitlab.eclipse.org/eclipse/tsf/tsf/-/issues/475
Best regards
Sam
--
Sam Thursfield (he/him), Software Engineer
Codethink Ltd. http://www.codethink.co.uk/
