Ticket #533 (closed requirement: invalid)

Opened 4 years ago

Last modified 3 years ago

The performance of CKAN shall scale

Reported by: johnbywater Owned by:
Priority: awaiting triage Milestone: ckan-v1.3
Component: ckan Keywords:
Cc: Repository:


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.

How many machines can you have before the database becomes the bottleneck? At that point, what QoS can be obtained with normal hardware?

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?

Are there any other options for scaling the persistence mechanism?

Change History

comment:1 Changed 3 years ago by dread

  • Priority set to awaiting triage
  • Status changed from new to closed
  • Resolution set to invalid

Not a current issue afaik.

Note: See TracTickets for help on using tickets.