Custom Query (2152 matches)
Results (910 - 912 of 2152)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1345 | fixed | Investigate possible memory leak | kindly | nils.toedtmann |
Description |
There is some evidence pointing to CKAN handling memory inefficiently or even leaking under certain conditions: When we migrated ckan.net/thedatahub.org from eu7.okfn.org (32bit) to s053.okserver.org (64bit) (ticket) we experienced extraordinary memory usage peaks (ticket). Here are the observed value with Apache default settings:
William reduced the life-time of a WSGI CKAN process from 500 requests down to 25 requests (changeset). This (together with two other tweaks) changed the situation drastically:
This suggests that the more requests a CKAN processes serves over time, the more memory it consumes, aka bad memory management or a leak. To prove this theory, one could reduce the total number of WSGI CKAN processes as much as possible without killing the performance (e.g. down to processes=3), and then observing the relation between maximum-requests=25...500 and memory consumption. On 14/09/11 17:49, David Read wrote:
+1 |
|||
#1415 | fixed | Comments on current status of ckan deb packages | thejimmyg | nils.toedtmann |
Description |
This is a scratch pad ticket with some comments on the current status of our ckan deb packages. I know that some of it is the deb packaging roadmap anyway, please forgive me if i mention them here again. Rufus and me re-deployed some community ckan instances onto s022 (see http://trac.okfn.org/ticket/926). We followed the documentation http://docs.ckan.org/en/latest/install-from-package.html
|
|||
#206 | fixed | UI review | nickstenning | nickstenning |
Description |
Investigate and list (on the wiki at wiki:UiReviewNotes) CKAN's UI issues, in particular:
Est cost: 2 hrs. |