<div dir="ltr">Keeping debug symbols in binaries will result in poor performance, or it should<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Feb 14, 2013 at 4:47 PM, Asher Feldman <span dir="ltr"><<a href="mailto:afeldman@wikimedia.org" target="_blank">afeldman@wikimedia.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">For most projects, I recommend using the official packages available via<br>
the MariaDB projects own apt repo.<br>
<br>
The official packages are based on the Debian mysql packaging where<br>
installing the server package also installs a default database created<br>
around generic config defaults, a debian mysql maintenance user with a<br>
randomly generated password, and scripts (including init) that assume<br>
privileged access via that user. That is, installing the packages provides<br>
you with a fresh running working database with generic defaults suitable<br>
for a small server, and certain admin tasks automated. I think that's what<br>
the average labs and general users wants and expects.<br>
<br>
The packages I've built for production use at wmf strips out all of the<br>
debianisms, the debian project script rewrites, the pre/post install<br>
actions. They also leave debug symbols in the binaries and have compiler<br>
flag tweaks, but do not at this stage contain any source<br>
patches. Installing the server package doesn't create a default db, or<br>
provide an environment where you can even start the server on a fresh sever<br>
install without further work. Probably not a good choice for most labs<br>
users.<br>
<div class="im"><br>
On Wednesday, February 13, 2013, Petr Bena wrote:<br>
<br>
> thanks for updates.<br>
><br>
> Can you tell me what is a difference between maria db you are using and<br>
> the version that is recommended for use on ubuntu?<br>
><br>
><br>
</div>> On Wed, Feb 13, 2013 at 6:58 PM, Asher Feldman <<a href="mailto:afeldman@wikimedia.org">afeldman@wikimedia.org</a><javascript:_e({}, 'cvml', '<a href="mailto:afeldman@wikimedia.org">afeldman@wikimedia.org</a>');><br>
<div><div class="h5">> > wrote:<br>
><br>
>> The production migration to MariaDB was paused for a time by the EQIAD<br>
>> datacenter migration and issues involving other projects that took up my<br>
>> time, but the trial production roll-out will resume this month. All signs<br>
>> still point to our using it in production.<br>
>><br>
>> I did a lot of query testing on an enwiki MariaDB 5.5 slave over the<br>
>> course<br>
>> of more than a month before the first production deployment. Major<br>
>> version<br>
>> migrations with mysql and derivatives are not to be taken lightly in<br>
>> production environments. At a minimum, one must be concerned about query<br>
>> optimizer changes making one particular query type significantly slower.<br>
>> In the case of the switch to 5.5, there are several default behavior<br>
>> changes over 5.1 that can break applications or change results. Hence,<br>
>> some serious work over a plodding time frame before that first production<br>
>> slave switch.<br>
>><br>
>> Despite those efforts, a couple weeks after the switch, I saw a query<br>
>> generated by what seems to be a very rare edge case from that AFTv4<br>
>> extension that violated stricter enforcement of unsigned integer types in<br>
>> 5.5, breaking replication and requiring one off rewriting and execution of<br>
>> the query locally to ensure data consistency before skipping over it. I<br>
>> opened a bug, Mathias fixed the extension, and I haven't seen any other<br>
>> compatibility issues from AFTv4 or anything else deployed on enwiki.<br>
>><br>
>> That said, other projects utilize different extensions, so all of my<br>
>> testing that has gone into enwiki cannot be assumed to fully cover<br>
>> everything else. Because of that, and because I want to continue<br>
>> proceeding with caution for all of our projects, this will continue to be<br>
>> a<br>
>> slow and methodical process at this stage. Bugs in extensions that aren't<br>
>> used by English Wikipedia may be found and require fixing along the way.<br>
>><br>
>> As the MariaDB roll-out proceeds, I will provide updates on wikitech-l.<br>
>><br>
>> Best,<br>
>> Asher<br>
>><br>
</div></div>>> On Wed, Feb 13, 2013 at 5:19 AM, Petr Bena <<a href="mailto:benapetr@gmail.com">benapetr@gmail.com</a><javascript:_e({}, 'cvml', '<a href="mailto:benapetr@gmail.com">benapetr@gmail.com</a>');>><br>
<div class="im">>> wrote:<br>
>><br>
>> > Okay - so what is outcome? Should we migrate beta cluster? Are we going<br>
>> to<br>
>> > use it in production?<br>
>> ><br>
>> ><br>
</div>>> > On Wed, Feb 13, 2013 at 2:08 PM, Chad <<a href="mailto:innocentkiller@gmail.com">innocentkiller@gmail.com</a><javascript:_e({}, 'cvml', '<a href="mailto:innocentkiller@gmail.com">innocentkiller@gmail.com</a>');>><br>
>> wrote:<br>
>> ><br>
>> >> On Wed, Feb 13, 2013 at 8:05 AM, bawolff <<a href="mailto:bawolff%2Bwn@gmail.com">bawolff+wn@gmail.com</a><javascript:_e({}, 'cvml', '<a href="mailto:bawolff%252Bwn@gmail.com">bawolff%2Bwn@gmail.com</a>');>><br>
<div class="im">>> wrote:<br>
>> >> > Umm there was a thread several months ago about how it is used on<br>
>> >> several<br>
>> >> > of the slave dbs, if I recall.<br>
>> >> ><br>
>> >><br>
>> >> Indeed, you're looking for "mariadb 5.5 in production for english<br>
>> >> wikipedia"<br>
>> >><br>
>> >> <a href="http://www.gossamer-threads.com/lists/wiki/wikitech/319925" target="_blank">http://www.gossamer-threads.com/lists/wiki/wikitech/319925</a><br>
>> >><br>
>> >> -Chad<br>
>> >><br>
>> >> _______________________________________________<br>
>> >> Wikitech-l mailing list<br>
</div>>> >> <a href="mailto:Wikitech-l@lists.wikimedia.org">Wikitech-l@lists.wikimedia.org</a> <javascript:_e({}, 'cvml',<br>
>> '<a href="mailto:Wikitech-l@lists.wikimedia.org">Wikitech-l@lists.wikimedia.org</a>');><br>
<div class="im">>> >> <a href="https://lists.wikimedia.org/mailman/listinfo/wikitech-l" target="_blank">https://lists.wikimedia.org/mailman/listinfo/wikitech-l</a><br>
>> >><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Labs-l mailing list<br>
</div>>> > <a href="mailto:Labs-l@lists.wikimedia.org">Labs-l@lists.wikimedia.org</a> <javascript:_e({}, 'cvml',<br>
>> '<a href="mailto:Labs-l@lists.wikimedia.org">Labs-l@lists.wikimedia.org</a>');><br>
<div class="im">>> > <a href="https://lists.wikimedia.org/mailman/listinfo/labs-l" target="_blank">https://lists.wikimedia.org/mailman/listinfo/labs-l</a><br>
>> ><br>
>> ><br>
>> _______________________________________________<br>
>> Wikitech-l mailing list<br>
</div>>> <a href="mailto:Wikitech-l@lists.wikimedia.org">Wikitech-l@lists.wikimedia.org</a> <javascript:_e({}, 'cvml',<br>
>> '<a href="mailto:Wikitech-l@lists.wikimedia.org">Wikitech-l@lists.wikimedia.org</a>');><br>
>> <a href="https://lists.wikimedia.org/mailman/listinfo/wikitech-l" target="_blank">https://lists.wikimedia.org/mailman/listinfo/wikitech-l</a><br>
<div class="HOEnZb"><div class="h5">>><br>
><br>
><br>
_______________________________________________<br>
Wikitech-l mailing list<br>
<a href="mailto:Wikitech-l@lists.wikimedia.org">Wikitech-l@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/wikitech-l" target="_blank">https://lists.wikimedia.org/mailman/listinfo/wikitech-l</a></div></div></blockquote></div><br></div>