Motivation
If I understand correctly, the speed up of envpool comes from c++ implementation as supposed to python. So, I wonder if the XLA interface will provide anymore speed up when jitted by jax, which can then be further fused with NN policy using jax.lax.scan. It would be nice to have a benchmark for the XLA version of the environments. I suppose different hardware would yield different results, which is useful for deciding when to jit or not to jit the environment.
Solution
Benchmark of non-jitted XLA vs jitted XLA vs the default c++ implementation
Checklist
- [ x ] I have checked that there is no similar issue in the repo (required)
Motivation
If I understand correctly, the speed up of envpool comes from c++ implementation as supposed to python. So, I wonder if the XLA interface will provide anymore speed up when jitted by
jax, which can then be further fused with NN policy usingjax.lax.scan. It would be nice to have a benchmark for the XLA version of the environments. I suppose different hardware would yield different results, which is useful for deciding when to jit or not to jit the environment.Solution
Benchmark of non-jitted XLA vs jitted XLA vs the default c++ implementation
Checklist