[Koha-devel] Stack smashing resolved -- we think

[Chadwick, John, DCA]

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 at 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.
______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20100111/c5668db4/attachment-0003.htm>