Hi Ferran: On Thu, 03 Mar 2011, Ferran Jorba wrote: > I've looked at them and I have noticed, embarrassingly, that we have a > lot of room for improvement, as we have a much lower values (probably > Debian defaults; I'm not an expert at all) for our 8 GB server.
MySQL comes with example configurations; on Debian, see under /usr/share/doc/mysql-server-5.1/examples. You can typically take my-huge.cnf with good results. (Especially since at DDD you don't have 2M of records with 20M citation pairs, so my-huge.cnf should be already fine for you.) BTW, I have put up some notes about MySQL tuning on our old wiki: <https://twiki.cern.ch/twiki/bin/view/CDS/InvenioTuning#1_Tuning_MySQL> The max_connections part on the wiki and musings about the number of Apache processes are applicable when you run mod_python of mod_wsgi embedded mode. With mod_wsgi daemon mode, only the backend daemons are connecting to MySQL, so things are much better from this point of view. I'll refresh the page a bit when moving it to Trac, in a few weeks. > I have been waiting for a follow up from her question about > max_allowed_packet, but as I haven't received any, I'd like to ask > now. (Yeah, I hope to get to replying to Cornelia one of these days.) Bigger max_allowed_packet is needed for serialised Python objects, especially big citation dictionaries that are living as single blobs. If you don't use citation ranking on your Invenio instance, then the default max_allowed_packet value should be just fine. Otherwise you can raise it to something like 100M or 1G, depending on the number of citer-citee pairs. Best regards -- Tibor Simko
