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
As of now, each Resource object owns a ChunkedList< ResourceUsageEntry >, which will be accesed by init_graph() and delete_from_resources() .
However this resource-user-list will contain all tasks from all TaskSpaces even though only those in the current task space are relevant for init_graph().
We could eliminate this check if we have a separate resource-user-list for each TaskSpacexResource.
Also, the ResourceAccess would not need a shared_ptr to the resource-struct anymore . It only requires a Key ( Resource-id ) to look up the resource-user-list from a map in the TaskSpace once per init_task() , and then iteration over all resources will be more efficient.
The text was updated successfully, but these errors were encountered:
As of now, each
Resource
object owns aChunkedList< ResourceUsageEntry >
, which will be accesed byinit_graph()
anddelete_from_resources()
.However this resource-user-list will contain all tasks from all TaskSpaces even though only those in the current task space are relevant for
init_graph()
.We could eliminate this check if we have a separate resource-user-list for each
TaskSpace
xResource
.Also, the ResourceAccess would not need a
shared_ptr
to the resource-struct anymore . It only requires a Key ( Resource-id ) to look up the resource-user-list from a map in the TaskSpace once perinit_task()
, and then iteration over all resources will be more efficient.The text was updated successfully, but these errors were encountered: