Sigh,<br><br>You just took it up a notch in terms of disdain and sarcasm.<br>Why do people always only apologize sarcastically?<br><br>I asked you to try the -hp and turn off the monotonic clock just to gather the results to help you. You completely missed it and just went on about the threads. Please save the "ok fine the code is perfect, blah blah" if you would have just read the email and answered the question I might have cared more about the status of your problem.<br>
<br>I told you both of those threads need to be on their toes because they try to balance between a certian number of sql stmts or 500ms whatever comes first. When there are thousands of events per second being turned into SQL statements which are in turn compiled into large sql transactions.<br>
<br>If you want to come up with a way that they can sleep longer until there is a sign of activity and stay busy for a few seconds then slow down again, that's probably possible but the process is already idle at 0% cpu so maybe you can appreciate why we are not rushing to work on it. Maybe I'll give it a go just to show you it has nothing to do with your problem.<br>
<br>Please don't mock our comment about several years. You have no idea how hard this code was to develop and it's truly insulting. Its clear to see you are locked into assuming that the busy threads that are not all that busy because they are constantly yielding to the scheduler is breaking the timing code. I begged you to understand me when i told you that the err is not normal, most boxes do not see it doing nothing and there has to be a specific problem on your box or configuration. So instead of working with us you want to escalate to snotty comments. That's pretty normal on the internet I guess..... If you want to have a constructive conversation about our core, install FS on a normal box, use it for a few weeks, figure out everything about how it works then try.... There was pure speculation and conjecture in your original emails and I never said a word about it until you kept pushing.<br>
<br>Kristian mentioned he never sees that on that same hardware did you even consider following up on why that is?<br><br>I don't have your device, but I assume if you get it working well it will certainly help you more than it helps me so you could at least have the decency to believe what we are trying to tell you.<br>
<br><br><br><br><br><br><br><div class="gmail_quote">On Thu, Dec 3, 2009 at 3:44 PM, eaf <span dir="ltr"><<a href="mailto:erandr-junk@usa.net">erandr-junk@usa.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Oh, you mean giving FS higher priority? Yeah, as a last resort I'll do that.<br>
At the moment, I hope it won't be necessary as I can make those "hyper"<br>
threads behave, and will see how that goes first. I see where your<br>
implementation could be coming from. There is a queue of SQL queries in<br>
sofia.c processed by the worker thread. There are only two pop functions<br>
available in APR: queue_pop() and queue_trypop(), so alas no option with a<br>
timeout here. You don't want to block the thread in pop() indefinitely<br>
because you chose that same worker needs to do ireg and gw processing once<br>
in a while (separated by tens or hundreds of seconds, btw). You also want to<br>
be able to detect shutdown condition so that the worker doesn't hold up<br>
profile thread. So you chose to poll for events every millisecond instead of<br>
just creating an apr_thread_cond_t for resource friendly signalling.<br>
<br>
I agree that the timer thread philosophy is great and was the right choice<br>
for scaling, but I just don't comprehend responses to things like these<br>
other SQL or sofia worker threads. Did somebody even remotely acknowledge<br>
that busy loops at least in those areas that I showed may probably be a bad<br>
idea and could've been eliminated? I've heard suggestions to bump up<br>
priority, I've heard that the code was perfect already, that it's the result<br>
of 4-year effort, that I am arrogant, don't listen and don't understand<br>
squat.<br>
<br>
I'm sorry if I gave you impression that I was looking for the bad parts in<br>
the software. I apologized for that already. All I wanted was to have<br>
constructive conversation, perhaps I'm not too good at it. Code is already<br>
perfect according to you? Fine with me.<br>
<div><div></div><div class="h5"><br>
<br>
Anthony Minessale-2 wrote:<br>
><br>
> no,<br>
><br>
> I mean the one after that that you must have completely skipped with a<br>
> command line option to try and a param to set in the config. It somewhat<br>
> annoys me for taking the time to compose it now. I wrote all of the code<br>
> you are talking about myself and I was trying to give you some<br>
> suggestions....<br>
><br>
> Well, actually, you did answer my question about the platform so you must<br>
> have seen it.....<br>
><br>
> The loops are not the cause of that migration message, something wrong<br>
> with<br>
> the hardware or the kernel is.<br>
> Another guy just told you he does not see that problem on the same exact<br>
> hardware.<br>
><br>
> Even if you have a point about the sql threads, you could make a patch to<br>
> slow them down but you cant slow down too much or you will not be able to<br>
> handle 400 cps all asking to send updates to transactions in batches of<br>
> thousands of sql stmts. Every line of that code is carefully designed so<br>
> I<br>
> don't know what else to tell you but to stop being so arrogant and re-read<br>
> this thread for all the advice you have totally ignored. I started out<br>
> trying to help you but I have a lot of work to do. I thoroughly explained<br>
> it to you and you are choosing to ignore me so I guess I'm done.<br>
> You can do whatever you want with your working copy, i'll see you in 3 or<br>
> 4<br>
> years when you get up to speed with the rest of us........<br>
><br>
><br>
<br>
</div></div><font color="#888888">--<br>
View this message in context: <a href="http://old.nabble.com/Choppy-sound-with-PCMU-tp26594250p26633739.html" target="_blank">http://old.nabble.com/Choppy-sound-with-PCMU-tp26594250p26633739.html</a><br>
</font><div><div></div><div class="h5">Sent from the Freeswitch-users mailing list archive at Nabble.com.<br>
<br>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
Twitter: <a href="http://twitter.com/FreeSWITCH_wire">http://twitter.com/FreeSWITCH_wire</a><br><br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>pstn:213-799-1400<br>