Skip to content

Releases: tak1n/reifier

v0.6.0

28 Feb 15:10
Compare
Choose a tag to compare

Until now even if no worker count was specified the server was started in clustered mode with a master process and 1 worker process where the threadpool was run.
This lead to the effect that rails was not able to hot reload the code in development mode even with no workers specified.
Users now need to explicit determine the workers to start in clustered mode.

v0.5.0

19 Feb 22:09
Compare
Choose a tag to compare

Using Futures with a ThreadPoolExecutor injected.
This means a user can now specify min threads and max threads used for each process.

be rackup -s reifier -O MinThreads=8 -O MaxThreads=16