worker_killer 0.1.0.19842 → 0.1.0.19844
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/README.md +9 -0
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: f35f1ea9a4591062e331c861888dbe5119191e94510e42d3900ab0826ccfad9f
|
|
4
|
+
data.tar.gz: 170b036d6c77ffbc483318f683479266d05df0a97af83ed417f27b8b2fdc380e
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 036ca0c4a7f7107c6c793b094f6f93282a54a3c053b7080f14fdea1ef3211aa806d2e336483e09ea59153ddb209229d64dd0af577d34268f599dac76e43e8f6a
|
|
7
|
+
data.tar.gz: 41c34fa4b40ce654871bb1f1b6e6a0591894d7aa10e546848dc2778b2ddcc8f34eef3dbd6b3a14b15f80b76a4c4d0970a3c3479eb5a3b779a0e0c6bd0e3e57f9
|
data/README.md
CHANGED
|
@@ -1,5 +1,14 @@
|
|
|
1
1
|
# worker-killer
|
|
2
2
|
|
|
3
|
+
[](https://rubygems.org/gems/worker_killer)
|
|
4
|
+
[](https://rubygems.org/gems/worker_killer/versions)
|
|
5
|
+
[](http://www.rubydoc.info/gems/worker_killer)
|
|
6
|
+
|
|
7
|
+
[](https://lysander.x.rnds.pro/api/v1/badges/wkiller_coverage.html)
|
|
8
|
+
[](https://lysander.x.rnds.pro/api/v1/badges/wkiller_quality.html)
|
|
9
|
+
[](https://lysander.x.rnds.pro/api/v1/badges/wkiller_outdated.html)
|
|
10
|
+
[](https://lysander.x.rnds.pro/api/v1/badges/wkiller_vulnerable.html)
|
|
11
|
+
|
|
3
12
|
Kill any workers by memory and request counts or take custom reaction. Inspired by [unicorn-worker-killer](https://github.com/kzk/unicorn-worker-killer).
|
|
4
13
|
|
|
5
14
|
`worker-killer` gem provides automatic restart of Web-server based on 1) max number of requests, and 2) process memory size (RSS). This will greatly improves site's stability by avoiding unexpected memory exhaustion at the application nodes.
|