Persistent/Clear vs TempJob allocations - continuation

[koirat]

Continuing the discussion from Persistent/Clear vs TempJob allocations:

@tertle

Depends on container, for example a clear on native list just sets length to 0. Doubt any allocation will be faster than that. In general most clears are pretty fast like this, and the ones that aren’t like hashmap call clear on allocation anyway…

I’m resurrecting this thread since I was not able to find answer to this question.
Lets say I have got MySystem.OnUpdate that operates on the similar data every frame using the some jobs. This jobs are producing and consuming objects using NativeList. The number of objects will be quite similar every frame.

In pure c# I would not recreate this list but reuse it. So in similar fashion i used Allocator.Persistant.

Now the question is is there a random access speed difference between Allocator.Persistant and Allocator.TempJob.

So should I rather allocate and dispose every frame using Alocator.TempJob.