* because wrapper-scripts are a bad idea on modern linux distributions and mysqld_safe is not needed there * because rpmbuild's automatic depsolve get useless without * because 99 out of 100 applications have configure-switches to build with- or without optional libraries BUT the resulting binary has clear dependencies * because LD_PRELOAD is nothing more than a hack example why mysqld_safe is no longer needed and this runs in production since 2011 on a couple of servers [root@srv-rhsoft:~]$ systemctl status mysqld.service mysqld.service - MySQL Database Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled) Active: active (running) since Mi 2013-04-24 19:20:45 CEST; 1 day 22h ago Main PID: 2312 (mysqld) CGroup: name=systemd:/system/mysqld.service └─2312 /usr/libexec/mysqld --defaults-file=/etc/my.cnf --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/lib/mysql/mysql.sock --open-files-limit=500000 --basedir=/usr --user=mysql Am 26.04.2013 09:26, schrieb Vladislav Vaintroub:
Mark, your links do not tell me why build dependency is good.
Yes, yes, malloc() replacement du jour is nice, is fast, will bring peace to Middle East.. but it is extremely easy to setup on Linux. So, my question depends why would anyone want to have *build* dependency, remains unanswered.
*From:*MARK CALLAGHAN [mailto:mdcallag@gmail.com] *Sent:* Freitag, 26. April 2013 08:16 *To:* Vladislav Vaintroub *Cc:* Kristian Nielsen; Daniel Bartholomew; maria-developers@lists.launchpad.net *Subject:* Re: [Maria-developers] Installing jemalloc on build VMs
Educated snark is much better than uneducated snark. Why don't you take the time to understand why TokuDB benefits from jemalloc before suggesting they fix their code. mysqld has always been faster for me with tcmalloc & jemalloc versus glibc malloc. I don't recall much support from everyone at official MySQL when I was reporting those problem. Why didn't you fix mysqld back then so I didn't have to waste time on that?
http://mysqlha.blogspot.com/2009/01/double-sysbench-throughput-with_18.html http://mysqlha.blogspot.com/2008/12/make-mysql-faster-in-one-hour_14.html http://mysqlha.blogspot.com/2009/01/innodb-is-faster-tcmalloc-is-nice.html
On Thu, Apr 25, 2013 at 9:47 AM, Vladislav Vaintroub <wlad@montyprogram.com <mailto:wlad@montyprogram.com>> wrote:
-----Original Message----- From: Maria-developers [mailto:maria-developers- <mailto:maria-developers-> bounces+wlad=montyprogram.com@lists.launchpad.net <mailto:montyprogram.com@lists.launchpad.net>] On Behalf Of Kristian Nielsen Sent: Donnerstag, 25. April 2013 18:30 To: Daniel Bartholomew Cc: maria-developers@lists.launchpad.net <mailto:maria-developers@lists.launchpad.net> Subject: Re: [Maria-developers] Installing jemalloc on build VMs
It is said that tokutek "requires" jemalloc - maybe it would be better to
fix
tokutek to work with standard libraries?
I wanted to say the same. I do not understand quite how it is possible to rely on malloc replacement library - it is a replacement, it is typically handled at runtime (using LD_PRELOAD environment variable). Perhaps someone familiar with the subject can enlighten us on it