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! -- 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.
* 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
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
Did you checked your zebra server ? Also try to reindex. On Fri, Sep 4, 2015, 8:24 AM 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!
-- 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
Yes Ahmad we did that.. :) -----Original Message----- From: "Ahmad Amanullah Khan" <ahmadamanullahkhan@gmail.com> Sent: 4/9/2015 11:19 PM To: "Jerwyn" <os.jerwynfernandez@gmail.com>; "koha@lists.katipo.co.nz" <koha@lists.katipo.co.nz> Subject: Re: [Koha] Big Collection Did you checked your zebra server ? Also try to reindex. On Fri, Sep 4, 2015, 8:24 AM 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! -- 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
You should look at zebra logs for the query Koha is sending to Zebra, then run it directly using yaz-client. That will give you information about the search itself. Once you figure it is not zebra, look at the slow queries log from mysql. Btw, you seem to get that message from a reverse proxy... Maybe that's were the problem is... El 4/9/2015 12:24 a. m., "Jerwyn" <os.jerwynfernandez@gmail.com> escribió:
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!
-- 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
Hi, We serve more than 13.000.000 items with 1.000.000 users in one of our customers. I suggest to change MySQL and InnoDB performance tuning parameters. It's a good idea to cache the data. There should be proxy problems also. Mengu On 04-09-2015 06:22, Jerwyn 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!
-- 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
Really thanks a lot for your inputs guys! We were somehow able to optimize the server and it no longer receive errors. However the loading still loads too long. For a 50,000 search result it takes around 20-25 seconds. We are now planning to move to Percona as per advice here http://wiki.koha-community.org/wiki/Performance hope it will resolve the issue through this. Kind regards! -- View this message in context: http://koha.1045719.n5.nabble.com/Big-Collection-tp5852592p5853253.html Sent from the Koha-general mailing list archive at Nabble.com.
participants (6)
-
Ahmad Amanullah Khan -
Chris Cormack -
Jerwyn -
Jerwyn Fernandez
-
Mengu Yazicioglu -
Tomas Cohen Arazi