Comments on: Extending ltrace to make your Ruby/Python/Perl/PHP apps faster http://timetobleed.com/extending-ltrace-to-make-your-rubypythonperlphp-apps-faster/ technical ramblings from a wanna-be unix dinosaur Thu, 03 May 2012 05:40:26 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Hello world demystified « Commodity http://timetobleed.com/extending-ltrace-to-make-your-rubypythonperlphp-apps-faster/comment-page-1/#comment-849 Hello world demystified « Commodity Fri, 22 Oct 2010 01:23:52 +0000 http://timetobleed.com/?p=1058#comment-849 [...] Let see some Ruby (see if you can spot something peculiar!) [...] [...] Let see some Ruby (see if you can spot something peculiar!) [...]

]]> By: Joe Damato (ice799) http://timetobleed.com/extending-ltrace-to-make-your-rubypythonperlphp-apps-faster/comment-page-1/#comment-752 Joe Damato (ice799) Sat, 17 Jul 2010 07:50:36 +0000 http://timetobleed.com/?p=1058#comment-752 never heard back from the maintainer. he might be dead. no idea. all my codes are on github, though and you can clone and build ltrace from there. i pinged the maintainer again after i saw your comment and havent heard anything. never heard back from the maintainer. he might be dead. no idea. all my codes are on github, though and you can clone and build ltrace from there. i pinged the maintainer again after i saw your comment and havent heard anything.

]]> By: EvanCarroll http://timetobleed.com/extending-ltrace-to-make-your-rubypythonperlphp-apps-faster/comment-page-1/#comment-751 EvanCarroll Wed, 14 Jul 2010 10:39:53 +0000 http://timetobleed.com/?p=1058#comment-751 Did anything ever come of this, it would be nice to sum up this blog post with its official status. Did anything ever come of this, it would be nice to sum up this blog post with its official status.

]]> By: PM http://timetobleed.com/extending-ltrace-to-make-your-rubypythonperlphp-apps-faster/comment-page-1/#comment-440 PM Fri, 16 Oct 2009 21:05:04 +0000 http://timetobleed.com/?p=1058#comment-440 nice work, i'll try this, this week end. <br>May be not for mysql (since mysql already had the option log-slow-queries/mysqldumpslow), <br>but for many other stuff (sockets, graph report, extensions like Gd, ...)<br>thanks nice work, i'll try this, this week end.
May be not for mysql (since mysql already had the option log-slow-queries/mysqldumpslow),
but for many other stuff (sockets, graph report, extensions like Gd, …)
thanks

]]> By: tmm1 http://timetobleed.com/extending-ltrace-to-make-your-rubypythonperlphp-apps-faster/comment-page-1/#comment-435 tmm1 Mon, 12 Oct 2009 23:58:12 +0000 http://timetobleed.com/?p=1058#comment-435 Also ltrace can trace system calls, so you can use it instead of strace. Also ltrace can trace system calls, so you can use it instead of strace.

]]> By: tmm1 http://timetobleed.com/extending-ltrace-to-make-your-rubypythonperlphp-apps-faster/comment-page-1/#comment-436 tmm1 Mon, 12 Oct 2009 23:57:50 +0000 http://timetobleed.com/?p=1058#comment-436 Using strace to trace mysql traffic is painful. You have to know which file descriptors to trace (check via lsof first), then trace all network traffic on those fds in verbose mode to see the queries themselves (doesn't work if the mysql protocol has compression enabled), and then try to figure out how long each of the queries took to execute by matching queries and responses.<br><br>ltraceing mysql_send_query() gives you all this information in one line. Using strace to trace mysql traffic is painful. You have to know which file descriptors to trace (check via lsof first), then trace all network traffic on those fds in verbose mode to see the queries themselves (doesn't work if the mysql protocol has compression enabled), and then try to figure out how long each of the queries took to execute by matching queries and responses.

ltraceing mysql_send_query() gives you all this information in one line.

]]> By: rogerpack http://timetobleed.com/extending-ltrace-to-make-your-rubypythonperlphp-apps-faster/comment-page-1/#comment-434 rogerpack Mon, 12 Oct 2009 22:09:30 +0000 http://timetobleed.com/?p=1058#comment-434 True that might be useful for tracing more than just network related shtuffs.<br>-r True that might be useful for tracing more than just network related shtuffs.
-r

]]> By: ice799 http://timetobleed.com/extending-ltrace-to-make-your-rubypythonperlphp-apps-faster/comment-page-1/#comment-433 ice799 Mon, 12 Oct 2009 21:25:20 +0000 http://timetobleed.com/?p=1058#comment-433 Not as pretty and also *completely* different.<br><br>Try to trace garbage_collect, rb_thread_save_context, and rb_schedule using strace. You can't. Being able to trace these functions is really useful when diagnosing performance problems. Not as pretty and also *completely* different.

Try to trace garbage_collect, rb_thread_save_context, and rb_schedule using strace. You can't. Being able to trace these functions is really useful when diagnosing performance problems.

]]> By: rogerpack http://timetobleed.com/extending-ltrace-to-make-your-rubypythonperlphp-apps-faster/comment-page-1/#comment-432 rogerpack Mon, 12 Oct 2009 19:53:54 +0000 http://timetobleed.com/?p=1058#comment-432 %sudo strace -rp 26480 2>&1| egrep 'read|write'<br><br> 0.000047 write(3, "333select sleep(1) from users", 31) = 31<br> 0.000071 read(3, "1113623def10sleep(1)f?25"..., 16384) = 63<br> 1.001755 write(1, "#<Mysql::Result:0xb7bdae18>n", 28) = 28<br><br>Not as pretty. %sudo strace -rp 26480 2>&1| egrep 'read|write'

0.000047 write(3, “333select sleep(1) from users”, 31) = 31
0.000071 read(3, “1113623def10sleep(1)f?25”…, 16384) = 63
1.001755 write(1, “#<Mysql::Result:0xb7bdae18>n”, 28) = 28

Not as pretty.

]]> By: tmm1 http://timetobleed.com/extending-ltrace-to-make-your-rubypythonperlphp-apps-faster/comment-page-1/#comment-431 tmm1 Sun, 11 Oct 2009 12:33:09 +0000 http://timetobleed.com/?p=1058#comment-431 strace traces system calls. ltrace traces library calls. strace traces system calls. ltrace traces library calls.

]]>