Thank a lot for this Chris! We are still figuring out where the slow down is. Our suspect is MySQL as well, since we tried moving the database from other server to other like hosting it to locally, linode, amazon mc2 and digital ocean. Will take a look on this we really appreciate your help. Kind regards, On Fri, Sep 4, 2015 at 11:33 AM, Chris Cormack <chrisc@catalyst.net.nz> wrote:
* Jerwyn (os.jerwynfernandez@gmail.com) wrote:
Greetings!
We have roughly have 400,000 collections, cataloged in koha.
We are experiencing *"504 Gateway Time-out The server didn't respond in time."* whenever the keyword we are searching has a several of results.
Can you please give us inputs from your own experience on how are we going to optimize the server, to make it seamless.
Looking forward to this, thank you and best regards!
Hi Jerwyn
400,000 should be no problem, there are libraries with much bigger collections than that. Do you know where the slow down is?
MySQL would be my first suspect, but you will need to find where the slowdown is before you can optimise it.
You can have a look at http://wiki.koha-community.org/wiki/Performance
Chris
-- View this message in context:
http://koha.1045719.n5.nabble.com/Big-Collection-tp5852592.html
Sent from the Koha-general mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
-- - Jerwyn Fernandez, RL Koha Support Specialist OS Library Solutions​​ (63) 9336734607 (02) 7383209