thanks,
but let’s come back to the original issue, why the consumer is so slow using torch.tensor with torch.multiprocessing.Queue?  I would expect it can be resolved with a very simple fix to share tensors between processes with acceptable performance. Or we have to admit that the current implementation needs improvement …  and so other people (maybe me maybe not,  ) can start the work for the improvement when have bandwidth.