Custom Query (2152 matches)
Results (901 - 903 of 2152)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1339 | fixed | Issues / question re navl and data conversion | kindly | rgrp |
Description |
I ran into a bug with the size field on resources.
To solve this (cset:58acdcfe6d4e) i created an int_converter temporarily in logic/schema.py (this is almost certainly the wrong place). But I think it raises a bigger issue about the conversion layer and how it works. |
|||
#1344 | fixed | datetime error json conversion on search | kindly | kindly |
Description |
Json decoding error on search, due to date in resources. |
|||
#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 |