[ckan-dev] Bootup performance

Tue Apr 7 10:46:21 UTC 2015

Hi Steve,

Thanks for you answer. Our current docker setup segregates indeed the different instances in different containers ( 1x postgresql, 1x ckan, 1x solr).

In order to compare… could you please tell me a bit about your CKAN instance:
- How many datasets are currently hosted?
- What are the specs of the machines where CKAN runs?
- How long does it take aprox. for the CKAN instance to boot after a reset or shutdown ?

-- 
Alex Corbi

Am 7. April 2015 bei 12:14:14, Alex Corbi (a.corbi at gmail.com) schrieb:

Hi Everyone,

I have a performance question depending on amount of stored datasets and bootup times.

In the context of http://data.opendevelopmentmekong.net/, which is an instance based on CKAN v2.2.1 deployed through uwsgi on a server with 2core and 4GB of memory (using docker containers), currently with VERY low traffic and 13 datasets hosted. In this scneario, bootup times after restart of the docker container for CKAN are quick and does not present any issue.

However, the bootup time and derivated Issues increase considerably with the number of datasets. On the very same setup, but being populated with ~2000 datasets, the CKAN instance takes up to 20 minutes to boot and sometimes shows an erratic behaviour after rebooting ( Internal Server Errors, random URLs and resources not being loaded).

So, here my questions:
- Do the characteristics of the described system (number of datasets, traffic) comply with the "small to medium" instance type mentioned on https://github.com/ckan/ckan/wiki/Hardware-Requirements? Are 2 core/4GB mem ok?

- During the bootup process, activity on the CKAN and Postgresql side can be detected. both components take a big percentage of the CPU during the bootup (~20 minutes). What is supposed to be happening behind the scenes? Solr reindexing everytime CKAN restarts?

- Is there any possible action to be done in order to reduce the booting time of a restarted CKAN instance? (DB/Solr/ckan conf.)

Thanks in advance, any help is appreciated,

-- 
Alex Corbi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20150407/858943f3/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: Message signed with OpenPGP using AMPGpg
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20150407/858943f3/attachment-0003.sig>