You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that selecting a facet in the facet tree causes the facet value list to refresh twice, which certainly has a negative impact on performance. Also, this revealed a hard-to-find-but-now-fixed bug in the Sparql-Cache, which would return the result set of a prior execution of the same query. The second result set was then empty, because it was consumed by the logic following the first invocation.
In essence, all refresh routines of the jassa-ui components need to be checked for how often they are called per action.
The text was updated successfully, but these errors were encountered:
I noticed that selecting a facet in the facet tree causes the facet value list to refresh twice, which certainly has a negative impact on performance. Also, this revealed a hard-to-find-but-now-fixed bug in the Sparql-Cache, which would return the result set of a prior execution of the same query. The second result set was then empty, because it was consumed by the logic following the first invocation.
In essence, all refresh routines of the jassa-ui components need to be checked for how often they are called per action.
The text was updated successfully, but these errors were encountered: