Skip to content
This repository was archived by the owner on Aug 2, 2023. It is now read-only.

Multi-core support #33

Closed
3 tasks done
achimnol opened this issue Apr 27, 2017 · 0 comments
Closed
3 tasks done

Multi-core support #33

achimnol opened this issue Apr 27, 2017 · 0 comments
Assignees
@achimnol
Labels
feature

Comments

@achimnol
Copy link
Member

achimnol commented Apr 27, 2017 •
edited
Loading

For scalability, the gateway server must become multi-core enabled.
@achimnol achimnol self-assigned this Apr 27, 2017
achimnol added a commit that referenced this issue Apr 27, 2017
@achimnol
refs #33: Refactor server main using aiotools.
42c6780 
 * Multi-process mode is not enabled yet.
achimnol added a commit that referenced this issue Jun 2, 2017
@achimnol
refs #33: Rewrite to use Subscriber from sorna-common
9706f6c 
Still, dispatching mechanims is hand-brewed one...
achimnol added a commit that referenced this issue Aug 7, 2017
@achimnol
refs #33: Reviv EventServer as EventSubscriber with multi-core support
90332f6 
 * aiozmq.rpc uses PUSH/PULL ZMQ sockets - we can put a routing proxy
   so that it distributes incoming event messages to multiple manager
   worker processes (instead of complicated external MQ servers!).
achimnol added a commit that referenced this issue Aug 7, 2017
@achimnol
refs #33: "instance_terminated" by agent-lost no longer depends on Redis
b2f7bad 
 * For multiprocessing, it uses multiprocessing.Manager().dict().
   This may incur a little performance overhead but simplifies
   maintainability a lot.
achimnol added a commit that referenced this issue Aug 7, 2017
@achimnol
refs #33: Remove MQ-related configs
786d175
achimnol added a commit that referenced this issue Aug 7, 2017
@achimnol
refs #33: Fix use of unified event dispatcher
9356d69
achimnol added a commit that referenced this issue Aug 20, 2017
@achimnol
refs #31, #33: WIP for workstation migration
aef0fb4
achimnol added a commit that referenced this issue Aug 23, 2017
@achimnol
refs #8, #19, #28, #29, #31, #32, #33: Rewrite the manager core.
45eaafd 
 * Now manager + gateway runs on multiple CPU cores with sane
   transaction semantics.  Thanks to aiotools!

   - It no longer depends on Redis as a pub-sub broker nor a database.
     All communications are done via ZeroMQ with no centralized queue
     server.

   - Redis is used only for per-keypair rate-limiting.

 * Now the manager searches available agent to spawn new containers
   based on available memory / CPU / GPU capacity units.
   No more hard-coded instance types!

 * The db schema is now prepared for multi-container kernel sessions.

   - User-facing APIs now use "session ID" which is directed to the
     master container of the given session.

   - Each container has unique "kernel ID" and managed individually.

 * Replace asyncpg + asyncpgsa with aiopg for better SQLAlchemy
   supports (especially custom type decorators).

 * TODOs

   - Stabilize accounting of used/available resource units.

   - Still some parts are confused of session/kernel IDs...
achimnol added a commit that referenced this issue Aug 29, 2017
@achimnol
refs #33: Improve agent termination discovery and handling
f7e51a3 
 * No longer repeated "agent-lost" logs (only once!)
 * Moved agent-specific logic in gateway/events.py to gateway/kernel.py
 * Synchronize correctly when updating/reading the "last seen" dictionary shared by all worker processes
achimnol added a commit that referenced this issue Sep 18, 2017
@achimnol
refs #33: Let it scale with CPU cores on the system
53458c9 
 * Agent status checker coroutine now only runs on the first CPU core
 * Fix SQLAlchemy query in registry's enumerate_instance() method
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@achimnol achimnol

Labels
feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@achimnol