http://localhost/ticket/533 <p> CKAN uses a database. We can put the database on another machine and then clone the CKAN machine. Then there are two machines calling the database and converting SQL results into HTTP responses. </p> <p> How many machines can you have before the database becomes the bottleneck? At that point, what QoS can be obtained with normal hardware? </p> <p> Afterwards, can CKAN be made to scale further than this with a little development? Can its Postgres database be mirrored in realtime? Or can we change SQL writes (create/updates) to write to many databases? </p> <p> Are there any other options for scaling the persistence mechanism? </p> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/533 Trac 0.12.3 dread Tue, 21 Dec 2010 18:49:34 GMT http://localhost/ticket/533#comment:1 http://localhost/ticket/533#comment:1 <ul> <li><strong>priority</strong> set to <em>awaiting triage</em> </li> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>invalid</em> </li> </ul> <p> Not a current issue afaik. </p> Ticket