Custom Query (2152 matches)
Results (547 - 549 of 2152)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #237 | fixed | The system shall accept submissions from authenticated owners of activated accounts using the data openness enquiry form by presenting the enquiry summary and prompting for confirmation | johnbywater | johnbywater |
| #348 | fixed | The system shall accept package edit form submissions in an API | johnbywater | johnbywater |
| #533 | invalid | The performance of CKAN shall scale | johnbywater | |
| Description |
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? |
|||
Note: See TracQuery
for help on using queries.
