Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BOPTESST-Gym-service #101

Open
javiarrobas opened this issue Jun 22, 2022 · 2 comments
Open

BOPTESST-Gym-service #101

javiarrobas opened this issue Jun 22, 2022 · 2 comments
Labels
wontfix This will not be worked on

Comments

@javiarrobas
Copy link
Contributor

This issue is to accommodate BOPTEST-Gym to work with the service version of BOPTEST. For the moment, this new BOPTEST-Gym-service version will be developed in parallel with master, similarly to what happens with BOPTEST-master and BOPTEST-Service. It is also expected that BOPTEST-Gym-Service will enable easier parallelization during learning which may be a very interesting feature since the emulators can run on the cloud as vectorized environments.

@javiarrobas
Copy link
Contributor Author

Some benchmarking:

  • Testing with boptest-service locally:
    image

  • Testing with boptest-service in a remote server (AWS EC2 t2.xlarge 16 Gb instance):
    image

This means that, based on some of the tests with a co-simulation, we see that using service remotely is only ~55sec/32sec=1.7 or ~26sec/18sec=1.4 times slower. Note that using service remotely unleashes the possibility to launch several environments on the cloud with vectorized environments which may considerably speed up the time required to train RL agents (just having two environments would already be an advantage). This shows that vectorization is a very interesting feature to be implemented, especially when combining it with boptest-gym-service.

FYI @dhblum @kbenne @icupeiro.

@dhblum
Copy link
Collaborator

dhblum commented Jun 23, 2022

This sounds like good news indeed!

@javiarrobas javiarrobas added the wontfix This will not be worked on label Jul 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants