Deploy auto-lance and thread pool change
Bug #1259238 reported by
Paul Everitt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KARL3 |
Fix Released
|
Undecided
|
Paul Everitt |
Bug Description
We're seeing memory zoom up over 2 Gb on KARL app servers. We don't know if it is a leak. With 3 app servers each having 3 threads each, it is hard to tell from request to request what is due to cold cache.
Problems
- Can't isolate slow requests
- Using too much memory
Since we have 3 app servers, we don't really need 3 threads per app server. We're going to:
- Lower the threads to 2 (to conserve RAM and increase chance of cache hits)
- Put in autolance to kill the processes when they exceed a certain amount of memory
Changed in karl3: | |
status: | New → Fix Released |
To post a comment you must log in.
I need to get this deployed to production. Added Shane as nosy to FYI him that we're changing the thread pool size.