- Use gevent
- For now we start threads for each agent/connection/job/...
- This is inneficient, as most of them only wait for one or other socket (either from Docker or from RPyC)
- Using gevent will be faster and pose less stress to the OS, that is already way too stressed by Docker
- This needs some work:
- RPyC and Docker-py do not support gevent from scratch
- https://github.com/smurfix/playground/blob/master/Pinako/geventrpyc/__init__.py provides a gevent-compatible RPyC server
- Docker-py may work from scratch, as it uses only pythonic features, but this needs to be tested
- Websockets? To handle the task page (status update of jobs)
- probably needs gevent
- I love Socket.io
- Interactive tasks
- needs websockets
- probably a good way to extend INGInious to other type of exercices
- the 'ssh' debug mode should be implemented with an interactive task
- ...
Last active
September 2, 2015 14:22
-
-
Save GuillaumeDerval/fb219569c7e03a938f9b to your computer and use it in GitHub Desktop.
Roadmap 2 for INGInious
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment