puma_worker_killer 0.0.2 → 0.0.3
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/CHANGELOG.md +3 -0
- data/README.md +5 -1
- data/lib/puma_worker_killer/version.rb +2 -2
- data/puma_worker_killer.gemspec +2 -2
- metadata +7 -6
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: ad7e53791affc61948522399fb84ff1695c15e10
|
|
4
|
+
data.tar.gz: 1705c37b135041e88364c2f47ac6a59cceb6803d
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 14870594b03d9ec384b7f3bf6762c3d02f862b55d2ef5052db31578d9c8d852d2e08aaa46a4e277de5c68a210f634b416f3cc6a19ccefd09096dd325a625fc9a
|
|
7
|
+
data.tar.gz: f6be7f6cb196854986b572f62a4ea606091ed59dda4bb0e8c045f5d25e0f8b33587e65906194eea3ac3a0690455bd9039e96df5f8b7b5068f74a1b0600769bce
|
data/CHANGELOG.md
ADDED
data/README.md
CHANGED
|
@@ -5,7 +5,9 @@
|
|
|
5
5
|
|
|
6
6
|
## What
|
|
7
7
|
|
|
8
|
-
If you have a memory leak in your code, finding and plugging it can be a herculean effort. Instead what if you just killed your processes when they got to be too large? The Puma Worker Killer does just that. Similar to [Unicorn Worker Killer](https://github.com/kzk/unicorn-worker-killer) but for the Puma web server.
|
|
8
|
+
If you have a memory leak in your code, finding and plugging it can be a herculean effort. Instead what if you just killed your processes when they got to be too large? The Puma Worker Killer does just that. Similar to [Unicorn Worker Killer](https://github.com/kzk/unicorn-worker-killer) but for the Puma web server.
|
|
9
|
+
|
|
10
|
+
Puma worker killer can only function if you have enabled cluster mode or hybrid mode (threads + worker cluster). If you are only using threads (and not workers) then puma worker killer cannot help keep your memory in control.
|
|
9
11
|
|
|
10
12
|
|
|
11
13
|
## Install
|
|
@@ -20,6 +22,8 @@ Then run `$ bundle install`
|
|
|
20
22
|
|
|
21
23
|
## Use
|
|
22
24
|
|
|
25
|
+
> If you like `puma_worker_killer` consider using [puma_auto_tune instead](https://github.com/schneems/puma_auto_tune). It handles memory leaks and tunes your workers too!
|
|
26
|
+
|
|
23
27
|
Somewhere in your main process run this code:
|
|
24
28
|
|
|
25
29
|
```ruby
|
|
@@ -1,3 +1,3 @@
|
|
|
1
1
|
module PumaWorkerKiller
|
|
2
|
-
VERSION = "0.0.
|
|
3
|
-
end
|
|
2
|
+
VERSION = "0.0.3"
|
|
3
|
+
end
|
data/puma_worker_killer.gemspec
CHANGED
|
@@ -18,7 +18,7 @@ Gem::Specification.new do |gem|
|
|
|
18
18
|
gem.test_files = gem.files.grep(%r{^(test|spec|features)/})
|
|
19
19
|
gem.require_paths = ["lib"]
|
|
20
20
|
|
|
21
|
-
gem.add_dependency "puma", "~>
|
|
22
|
-
gem.add_dependency "get_process_mem", "~>
|
|
21
|
+
gem.add_dependency "puma", "~> 2.7"
|
|
22
|
+
gem.add_dependency "get_process_mem", "~> 0.1"
|
|
23
23
|
gem.add_development_dependency "rake", "~> 10.1"
|
|
24
24
|
end
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: puma_worker_killer
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.0.
|
|
4
|
+
version: 0.0.3
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Richard Schneeman
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2014-
|
|
11
|
+
date: 2014-04-03 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: puma
|
|
@@ -16,28 +16,28 @@ dependencies:
|
|
|
16
16
|
requirements:
|
|
17
17
|
- - "~>"
|
|
18
18
|
- !ruby/object:Gem::Version
|
|
19
|
-
version: '2'
|
|
19
|
+
version: '2.7'
|
|
20
20
|
type: :runtime
|
|
21
21
|
prerelease: false
|
|
22
22
|
version_requirements: !ruby/object:Gem::Requirement
|
|
23
23
|
requirements:
|
|
24
24
|
- - "~>"
|
|
25
25
|
- !ruby/object:Gem::Version
|
|
26
|
-
version: '2'
|
|
26
|
+
version: '2.7'
|
|
27
27
|
- !ruby/object:Gem::Dependency
|
|
28
28
|
name: get_process_mem
|
|
29
29
|
requirement: !ruby/object:Gem::Requirement
|
|
30
30
|
requirements:
|
|
31
31
|
- - "~>"
|
|
32
32
|
- !ruby/object:Gem::Version
|
|
33
|
-
version: '0'
|
|
33
|
+
version: '0.1'
|
|
34
34
|
type: :runtime
|
|
35
35
|
prerelease: false
|
|
36
36
|
version_requirements: !ruby/object:Gem::Requirement
|
|
37
37
|
requirements:
|
|
38
38
|
- - "~>"
|
|
39
39
|
- !ruby/object:Gem::Version
|
|
40
|
-
version: '0'
|
|
40
|
+
version: '0.1'
|
|
41
41
|
- !ruby/object:Gem::Dependency
|
|
42
42
|
name: rake
|
|
43
43
|
requirement: !ruby/object:Gem::Requirement
|
|
@@ -61,6 +61,7 @@ extra_rdoc_files: []
|
|
|
61
61
|
files:
|
|
62
62
|
- ".gitignore"
|
|
63
63
|
- ".travis.yml"
|
|
64
|
+
- CHANGELOG.md
|
|
64
65
|
- Gemfile
|
|
65
66
|
- README.md
|
|
66
67
|
- Rakefile
|