Author Response
Thank you for reviewing our paper and we appreciate your comments. Here are our responses to your questions:
> It would be beneficial to include MSRL in the experiments
We want to emphasize that **MSRL results have been included in the experiments already. Please refer to paragraph 2 in Section 4.1**.
We want to further clarify that **we have made our best effort to run the open-source code of MSRL. After we carefully checked the implementation, we have fully confirmed that the MSRL codebase cannot be examined in the same testing scenarios (with a similar scale) as we did**. In MSRL, each environment process requires an independent GPU for policy inference because it uses NCCL as the communication backend. Besides, we didn’t find a multi-learner option in the code. (See [code](https://github.com/mindspore-lab/mindrl/blob/master/mindspore_rl/algorithm/impala/impala_trainer.py).) These implementation choices limit the practical scalability of MSRL. In practice, we can utilize at most 8 CPU cores in the single-machine setting (64 cores for other methods) and at most 64 CPU cores in the distributed setting (700 cores for RLlib and 3200 cores for SRL). We believe this may not become a fair comparison with such a scalability difference. As a result, we did not include MSRL in our main results.
In addition, as a most sincere attempt to conduct a possible comparison between MSRL and our project, we evaluate SRL under the same setting as the MSRL paper (Section 6.2 Figure 6(a) in MSRL paper). In this setting, MSRL evaluated the PPO algorithm with 320 Mujoco Halfcheetah environments and 24 Nvidia V100 GPUs for inference. From the numbers in the MSRL paper, MSRL can finish one episode of 1000 steps in 3.85s resulting in 83116 FPS. In our experiment, SRL employs the same number of CPU cores and environment instances, but only need 4 Nvidia 3090 GPUs for inference. Even with 6x fewer GPUs, SRL achieves an overall training throughput of 210165 FPS, which is about 2.52x faster than the reported number of MSRL.
> Strengths: This paper presents a dataflow abstraction for RL training
> Weakness 1: Novelty against MSRL
We respectfully disagree with the reviewer with his/her comments about the contribution and novelty of this paper.
First, we remark that SRL’s contribution is much more than just a proposal of system abstractions. SRL is the first open-source system that can really perform efficient large-scale RL experiments over 15000 cores and reproduce OpenAI’s hide-and-seek project. Besides, SRL offers flexible and extensible interfaces such that users can effortlessly implement a new RL algorithm (see code snippets in Sec3.4 & App.A, various algorithm implementations in Sec.4.2). This paper also performs algorithm evaluation and confirms that insights provided by [1,2] extend to large-scale settings up to 15000 cores, i.e., larger batch sizes are usually beneficial to PPO’s performance. We also want to remark that these experimental and engineering efforts are appreciated by [reviewer Qkzp](https://openreview.net/forum?id=lajn1iROCu¬eId=ITT99z9ky8 ) and [bQuB
](https://openreview.net/forum?id=lajn1iROCu¬eId=gPmZgegemV) . We kindly hope the reviewer can consider these aspects when judging this paper.
Second, we have to emphasize that SRL’s abstraction indeed has novelty even compared with the concept proposed by MSRL. Although MSRL’s design concepts can implement both of SEED and IMPALA architectures, it does not provide additional solutions to *overcome their limitations caused by coupling*, as we emphasized and deeply discussed in Sec 2.2. In contrast, workers in SRL are completely decoupled, allowing massive parallelism and efficient resource utilization under large-scale settings.
[1] Bowen Baker, Ingmar Kanitscheider, Todor M. Markov, Yi Wu, Glenn Powell, Bob McGrew, and Igor Mordatch. Emergent tool use from multi-agent autocurricula
[2] Marcin Andrychowicz, Anton Raichuk, Piotr Stanczyk, Manu Orsini, Sertan Girgin, Raphael Marinier, ¨ Leonard Hussenot, Matthieu Geist, Olivier Pietquin, Marcin Michalski, Sylvain Gelly, and Olivier ´ Bachem. What matters for on-policy deep actor-critic methods? A large-scale study.
> Environment ring is also introduced in EnvPool.
We remark that EnvPool runs environments in a thread pool, resembling *parallelism*, while environment ring adopts the idea of *pipelining* between environment simulation and policy inference to reduce idle time.
>In order to provide a comprehensive understanding of where any gains come from, it would be valuable to include a breakdown ablation study
Please find the breakdown ablation studies in Appendix C. These results are deferred to appendix due to page limits. In ablation studies, we show the benefits from environment ring, GPU inference, and trainer worker prefetching. Moreover, we also study the effect of each worker type and offer practical recommendations on how to configure SRL to achieve the best practical performance.