| 00:55.02 | *** part/#asterisk-dev kharwell (kharwell@nat/digium/x-faomefvkgxbjqvyp) |
| 01:20.10 | *** join/#asterisk-dev infobot (ibot@rikers.org) |
| 01:20.10 | *** topic/#asterisk-dev is Asterisk Development Discussion -=- http://www.asterisk.org/developers -=- Tier 2 and 3.14159265 support is in #asterisk -=- Check out our blog! blogs.asterisk.org -=- Follow on Twitter at @AsteriskDev |
| 02:13.46 | *** join/#asterisk-dev leedm777 (~textual@2604:2d80:8404:ffae:8dcd:4efd:4a19:a2cf) |
| 02:13.46 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 02:24.23 | *** join/#asterisk-dev CELYA_ (~Thunderbi@2a01cb0583d31d005c4cd77279c3852a.ipv6.abo.wanadoo.fr) |
| 04:12.09 | *** join/#asterisk-dev moy (sid47040@gateway/web/irccloud.com/x-awhodkspfrbjephk) |
| 04:12.46 | *** join/#asterisk-dev darkunderlord (sid242683@gateway/web/irccloud.com/x-dxlbnmjlovvkswzs) |
| 04:14.06 | *** join/#asterisk-dev tm1000 (sid6728@gateway/web/irccloud.com/x-hxxleshovylwhopt) |
| 04:14.12 | *** join/#asterisk-dev DanQuinney (sid18169@gateway/web/irccloud.com/x-jkqnpodhjxxlqsvt) |
| 04:15.44 | *** join/#asterisk-dev file (sid178970@asterisk/developer-and-muffin-lover/file) |
| 04:15.44 | *** mode/#asterisk-dev [+o file] by ChanServ |
| 04:16.09 | *** join/#asterisk-dev GameGamer43 (sid5533@gateway/web/irccloud.com/x-tehwlexikmofjwkc) |
| 04:17.50 | *** join/#asterisk-dev X-Rob (X-Rob@gateway/web/irccloud.com/x-gdktwxwsxpeurubn) |
| 04:39.54 | *** join/#asterisk-dev bford (uid283514@gateway/web/irccloud.com/x-mfdmqrpcdylemdks) |
| 04:39.54 | *** mode/#asterisk-dev [+o bford] by ChanServ |
| 05:07.42 | *** join/#asterisk-dev Oooohboy (~Oooohboy@2605:6000:1711:c1ff:24c2:ef99:98:e75d) |
| 05:11.31 | *** join/#asterisk-dev elcontrastador (~textual@206.78.110.8) |
| 07:07.21 | *** join/#asterisk-dev CELYA_ (~Thunderbi@2a01:e0a:d:1111:8182:8270:e2e3:7103) |
| 08:03.08 | *** join/#asterisk-dev tsearle (~tsearle@37.19.10.33) |
| 08:03.08 | *** mode/#asterisk-dev [+o tsearle] by ChanServ |
| 08:14.11 | *** join/#asterisk-dev coreyfarrell (~coreyfarr@24-177-86-98.dhcp.nwtn.ct.charter.com) |
| 08:14.11 | *** mode/#asterisk-dev [+o coreyfarrell] by ChanServ |
| 08:25.52 | *** join/#asterisk-dev jkroon (~jkroon@uls-154-73-35-201.wall.uls.co.za) |
| 10:20.39 | *** join/#asterisk-dev stefan27 (~stefan27@static-212-247-4-149.cust.tele2.se) |
| 10:43.38 | *** join/#asterisk-dev elcontrastador (~textual@206.78.65.202) |
| 11:58.44 | *** join/#asterisk-dev pchero (~pchero@x1-6-d8-d7-75-5e-99-79.cpe.webspeed.dk) |
| 12:06.16 | *** join/#asterisk-dev pchero (~pchero@x1-6-d8-d7-75-5e-99-79.cpe.webspeed.dk) |
| 13:50.21 | *** join/#asterisk-dev leedm777 (textual@nat/digium/x-axlgyepgmbdzwcre) |
| 13:50.22 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 14:00.18 | jkroon | how bad is the impact of DEBUG_THREADS in terms of CPU performance? |
| 14:00.53 | gtjoseph | bad is relative. on a low volume system it probably won't be noticed |
| 14:01.10 | gtjoseph | on a high volume system, it depends on how much resources are available |
| 14:02.30 | jkroon | percentage wise? |
| 14:02.39 | *** join/#asterisk-dev hehol (~hehol@gatekeeper.loca.net) |
| 14:02.50 | jkroon | ie, if I normally see around 400% CPU according to top, what can I probably expect with it added? |
| 14:04.24 | jsmith | jkroon: My experience has been at least a doubling of load, sometimes more like tripling... but that's been a few years ago. |
| 14:04.39 | jsmith | jkroon: Things may have radically changed (for the better or for the worse) since. |
| 14:06.46 | jkroon | jsmith, thanks. i don't have sufficient CPU then on the system where I need it. |
| 14:44.46 | *** join/#asterisk-dev sduthil (~sduthil@modemcable094.94-70-69.static.videotron.ca) |
| 15:13.52 | *** join/#asterisk-dev kharwell (kharwell@nat/digium/x-yopjsyzsfaibylti) |
| 15:13.52 | *** mode/#asterisk-dev [+o kharwell] by ChanServ |
| 15:47.21 | *** join/#asterisk-dev file (sid178970@asterisk/developer-and-muffin-lover/file) |
| 15:47.21 | *** mode/#asterisk-dev [+o file] by ChanServ |
| 15:54.22 | *** join/#asterisk-dev Worldexe (~Worldexe@95.107.33.134) |
| 15:55.00 | *** join/#asterisk-dev rmudgett (rmudgett@nat/digium/x-bzxigsizrkikwbqx) |
| 15:55.00 | *** mode/#asterisk-dev [+o rmudgett] by ChanServ |
| 16:13.59 | *** join/#asterisk-dev leedm777 (textual@nat/digium/x-rmppcnzsbrtkxhpv) |
| 16:14.00 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 16:47.50 | *** join/#asterisk-dev rrittgarn (~rrittgarn@75-150-221-205-Illinois.hfc.comcastbusiness.net) |
| 16:58.31 | *** join/#asterisk-dev hehol (~hehol@gatekeeper.loca.net) |
| 17:04.55 | stefan27 | I have a vague memory of a compilation flag related to memory-leaks/references that could be used together with some ref***.py script to debug memory leaks in asterisk (possibly only those memoryleaks caused by ao2 stuff). I tested that stuff on asterisk 13.1 but if i recall correctly the compilation flag caused asterisk to be unnaturally slow. Has there been any improvements/new tools |
| 17:04.55 | stefan27 | introduced since 13.1->13.19? e.g. something like a lighter ref-debug mode? Is there a wiki page? |
| 17:06.46 | stefan27 | I have to leave the office shortly, but i'll catch any answers eventually if anyone knows and wants to respond :) |
| 17:12.44 | *** join/#asterisk-dev leedm777 (textual@nat/digium/x-opykaapcfmwkwqpr) |
| 17:12.45 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 17:15.06 | *** join/#asterisk-dev leedm777 (textual@nat/digium/x-kpnlyzyokuhckaek) |
| 17:15.06 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 17:25.43 | *** join/#asterisk-dev leedm777 (textual@nat/digium/x-lynozpocoubwsskb) |
| 17:25.43 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 17:55.17 | *** join/#asterisk-dev CELYA_ (~Thunderbi@2a01cb0583d31d00f0961b72fa757429.ipv6.abo.wanadoo.fr) |
| 17:56.38 | rmudgett | stefan27: https://wiki.asterisk.org/wiki/display/AST/Reference+Count+Debugging |
| 17:57.01 | rmudgett | Improvements have been made but they could not go into v13 because of API changes. |
| 17:57.32 | rmudgett | It is still going to slow things down because of all the reference logging that happens. |
| 19:02.03 | *** join/#asterisk-dev GameGamer43 (sid5533@gateway/web/irccloud.com/x-hvazegjwfuxgizne) |
| 19:14.58 | *** join/#asterisk-dev Demon_VoIP (~demon@109.60.222.253) |
| 19:34.31 | *** join/#asterisk-dev elcontrastador (~textual@70-90-215-98-BusName-ca.sacra.hfc.comcastbusiness.net) |
| 19:38.50 | *** join/#asterisk-dev pchero (~pchero@x1-6-d8-d7-75-5e-99-79.cpe.webspeed.dk) |
| 19:40.14 | *** join/#asterisk-dev pchero (~pchero@x1-6-d8-d7-75-5e-99-79.cpe.webspeed.dk) |
| 19:41.19 | *** part/#asterisk-dev kharwell (kharwell@nat/digium/x-yopjsyzsfaibylti) |
| 20:18.48 | coreyfarrell | stefan27: REF_DEBUG writes a lot of text to /var/log/asterisk/refs so putting the astlogdir on very fast storage could help. just be aware the refs file can grow large and rotation of this file is not supported. |
| 20:26.10 | coreyfarrell | in theory you could squeeze some extra performance out of it by patching main/astobj2.c to record less data by replacing fprintf arguments tag and func with "", this would write less data but not by much and it would make the results less usable. |
| 21:11.24 | *** join/#asterisk-dev Deeewayne (~dwayne@2605:a600:8052:b700:4be6:b3f6:15b3:1a03) |
| 21:11.24 | *** mode/#asterisk-dev [+o Deeewayne] by ChanServ |
| 21:36.31 | *** join/#asterisk-dev jkroon (~jkroon@165.16.204.165) |
| 21:51.37 | *** join/#asterisk-dev leedm777 (~textual@2604:2d80:8404:ffae:1439:95b4:5488:720a) |
| 21:51.37 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 22:05.53 | *** join/#asterisk-dev CELYA_1 (~Thunderbi@2a01cb0583d31d00f0961b72fa757429.ipv6.abo.wanadoo.fr) |
| 22:14.34 | *** join/#asterisk-dev coreyfarrell (~coreyfarr@24-177-86-98.dhcp.nwtn.ct.charter.com) |
| 22:14.34 | *** mode/#asterisk-dev [+o coreyfarrell] by ChanServ |
| 23:53.53 | *** join/#asterisk-dev leedm777 (~textual@2604:2d80:8404:ffae:5d60:32ac:5be5:745c) |
| 23:53.53 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |