The naming of ThreadPersistentData is a misleading description of its intended use and behaviour when compared with EntityPersistentData.
ThreadPersistentData is really more of a pooling mechanism for a heavy data type to allow jobs to avoid allocating instances on each iteration of a job, frame and across multiple jobs that use the same type.
The ThreadPersistentDataInstace is:
Globally shared between all Worlds
Does not get evaluated during World migration
Put some thought into the name but some ideas to riff on are:
The naming of
ThreadPersistentDatais a misleading description of its intended use and behaviour when compared withEntityPersistentData.ThreadPersistentDatais really more of a pooling mechanism for a heavy data type to allow jobs to avoid allocating instances on each iteration of a job, frame and across multiple jobs that use the same type.The
ThreadPersistentDataInstaceis:Put some thought into the name but some ideas to riff on are:
ParallelPooledDataProvider?