Okay, it looks like the stack smashing issue has been resolved through increased allocation of memory in several places on the MySQL server. Our server has 8GB of memory with a quad core processor. I allocated 1000GB to the MyISAM sort buffer size. I also increased the key buffer size. I found a few things about memory, but not much, on the Koha Wiki. I would like to hear from others what you have found to be optimal memory allocation for MySQL with about 20,000 bibs. Also, what would the optimal memory allocation for Zebra to use for indexing (or reindexing). Thanks, John Chadwick John.Chadwick@state.nm.us http://www.nmstatelibrary.org <http://www.nmstatelibrary.org/> Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System. ______________________________________________________________________ Confidentiality Notice: This e-mail,including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review,use,disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. This email has been scanned using Webroot Email Security. ______________________________________________________________________
Hi,
Our server has 8GB of memory with a quad core processor. I allocated 1000GB to the MyISAM sort buffer size. I also increased the key buffer size. I found a few things about memory, but not much, on the Koha Wiki. I would like to hear from others what you have found to be optimal memory allocation for MySQL with about 20,000 bibs. Also, what would the optimal memory allocation for Zebra to use for indexing (or reindexing).
which version of Koha do you have ? Koha 3.x uses all tables on InnoDB, so it is strange that you increse MyISAM sort buffer size. How many check in/out do you do every day ? And during your peack hours ? Bye Zeno Tajoli
2010/1/12 tajoli <tajoli@cilea.it>:
Hi,
Our server has 8GB of memory with a quad core processor. I allocated 1000GB to the MyISAM sort buffer size. I also increased the key buffer size. I found a few things about memory, but not much, on the Koha Wiki. I would like to hear from others what you have found to be optimal memory allocation for MySQL with about 20,000 bibs. Also, what would the optimal memory allocation for Zebra to use for indexing (or reindexing).
which version of Koha do you have ? Koha 3.x uses all tables on InnoDB, so it is strange that you increse MyISAM sort buffer size.
How many check in/out do you do every day ? And during your peack hours ?
It also seems strange that changing mysql, would stop zebra segfaulting. Chris
Hi,
Our server has 8GB of memory with a quad core processor. I allocated 1000GB to the MyISAM sort buffer size. I also increased the key buffer size. I found a few things about memory, but not much, on the Koha Wiki. I would like to hear from others what you have found to be optimal memory allocation for MySQL with about 20,000 bibs. Also, what would
We only found a couple of places in the Zebra configuration. One is for disk space for register and shadow files (default is 4GB) and the other deals with maximum memory which I bumped up. My rationale for the MySQL memory adjustments is in rebuilding the Zebra indexes Zebra indexes the data is being pulled from MySQL and when trying to rebuild the indexes with over 10,000 bibs we started seeing the memory errors. It was worth a shot. Also, I did find a few references on the Koha Wiki and in a few other places that use isam databases (Zebra) about memory allocation and MySQL. I would still like to see a healthy discussion about what the best practices are for allocating memory for Zebra and MySQL. Also, somewhat related to this, the zebraqueue table in MySQL. It seems to continue to build up with every load. Is this normal? Should the zebraqueue table in MySQL be cleared from time to time? Thanks, John -----Original Message----- From: Chris Cormack [mailto:chris@bigballofwax.co.nz] Sent: Monday, January 11, 2010 12:59 PM To: tajoli Cc: Chadwick, John, DCA; koha-devel@lists.koha.org Subject: Re: [Koha-devel] Stack smashing resolved -- we think 2010/1/12 tajoli <tajoli@cilea.it>: the
optimal memory allocation for Zebra to use for indexing (or reindexing).
which version of Koha do you have ? Koha 3.x uses all tables on InnoDB, so it is strange that you increse MyISAM sort buffer size.
How many check in/out do you do every day ? And during your peack hours ?
It also seems strange that changing mysql, would stop zebra segfaulting. Chris ______________________________________________________________________ This inbound email has been scanned for malicious software and transmitted safely to you using Webroot Email Security. ______________________________________________________________________ Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System. ______________________________________________________________________ Confidentiality Notice: This e-mail,including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review,use,disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. This email has been scanned using Webroot Email Security. ______________________________________________________________________
Hi,
Our server has 8GB of memory with a quad core processor. I allocated 1000GB to the MyISAM sort buffer size. I also increased the key buffer size. I found a few things about memory, but not much, on the Koha Wiki. I would like to hear from others what you have found to be optimal memory allocation for MySQL with about 20,000 bibs. Also, what would
Here is the link to the Wiki page that has some suggestions on MySQL settings. http://wiki.koha.org/doku.php?id=faq&s[]=memory&s[]=buffer The information about memory is about half way down the page. John -----Original Message----- From: Chris Cormack [mailto:chris@bigballofwax.co.nz] Sent: Monday, January 11, 2010 12:59 PM To: tajoli Cc: Chadwick, John, DCA; koha-devel@lists.koha.org Subject: Re: [Koha-devel] Stack smashing resolved -- we think 2010/1/12 tajoli <tajoli@cilea.it>: the
optimal memory allocation for Zebra to use for indexing (or reindexing).
which version of Koha do you have ? Koha 3.x uses all tables on InnoDB, so it is strange that you increse MyISAM sort buffer size.
How many check in/out do you do every day ? And during your peack hours ?
It also seems strange that changing mysql, would stop zebra segfaulting. Chris ______________________________________________________________________ This inbound email has been scanned for malicious software and transmitted safely to you using Webroot Email Security. ______________________________________________________________________ Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System. ______________________________________________________________________ Confidentiality Notice: This e-mail,including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review,use,disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. This email has been scanned using Webroot Email Security. ______________________________________________________________________
Our server has 8GB of memory with a quad core processor. I allocated 1000GB to the MyISAM sort buffer size. I also increased the key buffer size. I found a few things about memory, but not much, on the Koha Wiki. I would like to hear from others what you have found to be optimal memory allocation for MySQL with about 20,000 bibs. Also, what would
Right now we are building the system and adding records in 500 record chunks. John -----Original Message----- From: tajoli [mailto:tajoli@cilea.it] Sent: Monday, January 11, 2010 12:44 PM To: Chadwick, John, DCA Cc: koha-devel@lists.koha.org Subject: Re: [Koha-devel] Stack smashing resolved -- we think Hi, the
optimal memory allocation for Zebra to use for indexing (or reindexing).
which version of Koha do you have ? Koha 3.x uses all tables on InnoDB, so it is strange that you increse MyISAM sort buffer size. How many check in/out do you do every day ? And during your peack hours ? Bye Zeno Tajoli ______________________________________________________________________ This inbound email has been scanned for malicious software and transmitted safely to you using Webroot Email Security. ______________________________________________________________________ Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System. ______________________________________________________________________ Confidentiality Notice: This e-mail,including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review,use,disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. This email has been scanned using Webroot Email Security. ______________________________________________________________________
participants (3)
-
Chadwick, John, DCA -
Chris Cormack -
tajoli