Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-21 Thread Florian Smeets
On 20.08.12 10:32, Doug Barton wrote: On 08/15/2012 03:18, Alexander Motin wrote: It is quite pointless to speculate without real info like mentioned above KTR_SCHED traces. I'm sorry, you're quite wrong about that. In the cases I mentioned, and in about 2 out of 3 of the cases where users

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-20 Thread Doug Barton
On 08/15/2012 03:18, Alexander Motin wrote: On 15.08.2012 03:09, Doug Barton wrote: On 08/14/2012 12:20 PM, Adrian Chadd wrote: Would you be willing to compile a kernel with KTR so you can capture some KTR scheduler dumps? That way the scheduler peeps can feed this into schedgraph.py (and

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-20 Thread Alexander Motin
On 20.08.2012 11:32, Doug Barton wrote: On 08/15/2012 03:18, Alexander Motin wrote: On 15.08.2012 03:09, Doug Barton wrote: On 08/14/2012 12:20 PM, Adrian Chadd wrote: Would you be willing to compile a kernel with KTR so you can capture some KTR scheduler dumps? That way the scheduler peeps

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-20 Thread Doug Barton
On 08/20/2012 02:59, Alexander Motin wrote: On 20.08.2012 11:32, Doug Barton wrote: On 08/15/2012 03:18, Alexander Motin wrote: On 15.08.2012 03:09, Doug Barton wrote: On 08/14/2012 12:20 PM, Adrian Chadd wrote: Would you be willing to compile a kernel with KTR so you can capture some KTR

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-20 Thread Alexander Motin
On 20.08.2012 13:25, Doug Barton wrote: On 08/20/2012 02:59, Alexander Motin wrote: On 20.08.2012 11:32, Doug Barton wrote: On 08/15/2012 03:18, Alexander Motin wrote: On 15.08.2012 03:09, Doug Barton wrote: On 08/14/2012 12:20 PM, Adrian Chadd wrote: Would you be willing to compile a

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-20 Thread Doug Barton
On 08/20/2012 06:32, Alexander Motin wrote: I have no plans to converge them. I've just found problem in ULE, that was replicated into 4BSD and it would be strange to fix one without another. But fixing it exposed another old problem specific to 4BSD, which I fixed reusing logically equivalent

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-18 Thread Kevin Oberman
On Fri, Aug 17, 2012 at 3:23 PM, Ian Lepore free...@damnhippie.dyndns.org wrote: On Fri, 2012-08-17 at 14:29 -0700, Kevin Oberman wrote: On Fri, Aug 17, 2012 at 10:11 AM, Ian Lepore No! Not bde! He'll notice that I violated style(9) by accidentally leaving an extra blank line between a

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-18 Thread Lev Serebryakov
Hello, Ian. You wrote 17 августа 2012 г., 18:56:33: IL That result actually matches my expectation... it fixed only a part of IL your problem. I was (partly) wrong :( Under ``really high'' load (4MiB/s up/down load in same time) userland freezes again. Unfortunately, it is difficult to

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-17 Thread Lev Serebryakov
Hello, Ian. You wrote 16 августа 2012 г., 21:47:06: IL It's a long shot, but if the trouble you're seeing has the same cause, IL it should be fixed by this patch: IL http://lists.freebsd.org/pipermail/freebsd-hackers/2012-January/037233.html It looks like, this patch fixes freezes under

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-17 Thread Ian Lepore
On Fri, 2012-08-17 at 14:38 +0400, Lev Serebryakov wrote: Hello, Ian. You wrote 16 августа 2012 г., 21:47:06: IL It's a long shot, but if the trouble you're seeing has the same cause, IL it should be fixed by this patch: IL

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-17 Thread Adrian Chadd
On 17 August 2012 07:56, Ian Lepore free...@damnhippie.dyndns.org wrote: That result actually matches my expectation... it fixed only a part of your problem. I suspected (without very good evidence) that you may have two unrelated problems; hopefully now that we've eliminated one the other

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-17 Thread Ian Lepore
On Fri, 2012-08-17 at 09:58 -0700, Adrian Chadd wrote: On 17 August 2012 07:56, Ian Lepore free...@damnhippie.dyndns.org wrote: That result actually matches my expectation... it fixed only a part of your problem. I suspected (without very good evidence) that you may have two unrelated

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-17 Thread Kevin Oberman
On Fri, Aug 17, 2012 at 10:11 AM, Ian Lepore free...@damnhippie.dyndns.org wrote: On Fri, 2012-08-17 at 09:58 -0700, Adrian Chadd wrote: On 17 August 2012 07:56, Ian Lepore free...@damnhippie.dyndns.org wrote: That result actually matches my expectation... it fixed only a part of your

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-17 Thread Ian Lepore
On Fri, 2012-08-17 at 14:29 -0700, Kevin Oberman wrote: On Fri, Aug 17, 2012 at 10:11 AM, Ian Lepore No! Not bde! He'll notice that I violated style(9) by accidentally leaving an extra blank line between a comment block and the function definition. :) (There are probably more violations

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-17 Thread Adrian Chadd
.. I did mean bde because it's timekeeping related and he/mav are well versed in what's going on there. bde likely knows about the older RTC behaviours too. Sheesh. It's not always about style(9) :-) Adrian ___ freebsd-current@freebsd.org mailing

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-16 Thread Ian Lepore
On Wed, 2012-08-15 at 14:40 +0400, Lev Serebryakov wrote: Hello, Alexander. You wrote 15 августа 2012 г., 14:18:05: AM It is quite pointless to speculate without real info like mentioned AM above KTR_SCHED traces. Main thing I've learned about schedulers, things AM there never work as you

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-16 Thread Adrian Chadd
Hey cool; if this works out for lev, could we get this into -HEAD and MFC it? Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-16 Thread Lev Serebryakov
Hello, Ian. You wrote 16 августа 2012 г., 21:47:06: IL It's a long shot, but if the trouble you're seeing has the same cause, IL it should be fixed by this patch: IL http://lists.freebsd.org/pipermail/freebsd-hackers/2012-January/037233.html I'll add this patch to my tests, thanks! -- //

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-15 Thread Dimitry Andric
On 2012-08-15 02:09, Doug Barton wrote: On 08/14/2012 12:20 PM, Adrian Chadd wrote: ... Maybe things aren't being scheduled correctly and the added latency is killing performance? You might also try switching to SCHED_ULE to see if it helps. Most likely, s/ULE/4BSD/ here, and in the rest

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-15 Thread Lev Serebryakov
Hello, Adrian. You wrote 15 августа 2012 г., 2:20:48: AC Would you be willing to compile a kernel with KTR so you can capture AC some KTR scheduler dumps? AC That way the scheduler peeps can feed this into schedgraph.py (and you AC can too!) to figure out what's going on. AC Maybe things

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-15 Thread Lev Serebryakov
Hello, Lev. You wrote 15 августа 2012 г., 0:45:42: LS Answer looks trivial: router CPU is bottleneck. But here is one additional LS detail: `top' never shows less than 50% of idle when torrents are LS active. And `idle' time with torrents traffic is ALWAYS is higher than LS without them, but

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-15 Thread Doug Barton
On 08/14/2012 09:18 PM, Dimitry Andric wrote: On 2012-08-15 02:09, Doug Barton wrote: On 08/14/2012 12:20 PM, Adrian Chadd wrote: ... Maybe things aren't being scheduled correctly and the added latency is killing performance? You might also try switching to SCHED_ULE to see if it helps.

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-15 Thread Garrett Cooper
On Wed, Aug 15, 2012 at 1:21 AM, Lev Serebryakov l...@freebsd.org wrote: Hello, Lev. You wrote 15 августа 2012 г., 0:45:42: LS Answer looks trivial: router CPU is bottleneck. But here is one additional LS detail: `top' never shows less than 50% of idle when torrents are LS active. And

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-15 Thread Alexander Motin
On 15.08.2012 03:09, Doug Barton wrote: On 08/14/2012 12:20 PM, Adrian Chadd wrote: Would you be willing to compile a kernel with KTR so you can capture some KTR scheduler dumps? That way the scheduler peeps can feed this into schedgraph.py (and you can too!) to figure out what's going on.

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-15 Thread Lev Serebryakov
Hello, Alexander. You wrote 15 августа 2012 г., 14:18:05: AM It is quite pointless to speculate without real info like mentioned AM above KTR_SCHED traces. Main thing I've learned about schedulers, things AM there never work as you expect. There are two many factors are relations AM to predict

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-15 Thread Ian FREISLICH
Lev Serebryakov wrote: Hello, Lev. You wrote 15 =D0=B0=D0=B2=D0=B3=D1=83=D1=81=D1=82=D0=B0 2012 =D0=B3., 0:45:= 42: LS Answer looks trivial: router CPU is bottleneck. But here is one additi= onal LS detail: `top' never shows less than 50% of idle when torrents are LS active. And `idle'

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-15 Thread Lev Serebryakov
Hello, Ian. You wrote 15 августа 2012 г., 14:57:17: IF Are you sure it's a freeze and not a panic? I'm seeing very frequent Yes, I'm sure, because I have hardware console attached (serial one, connected to other computer on my network) and because it un-freeze after minute or two, and

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-15 Thread Alexander Motin
On 15.08.2012 13:40, Lev Serebryakov wrote: You wrote 15 августа 2012 г., 14:18:05: AM It is quite pointless to speculate without real info like mentioned AM above KTR_SCHED traces. Main thing I've learned about schedulers, things AM there never work as you expect. There are two many factors are

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-15 Thread Lev Serebryakov
Hello, Alexander. You wrote 15 августа 2012 г., 15:07:32: AM Yes, that is what I expected to see there. If you have timecounter other AM then i8254, you can release i8254 from those duties to allow using it as AM one-shot setting hint.attimer.0.timecounter=0. Otherwise there are no AM options

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-15 Thread Alexander Motin
On 15.08.2012 14:11, Lev Serebryakov wrote: Hello, Alexander. You wrote 15 августа 2012 г., 15:07:32: AM Yes, that is what I expected to see there. If you have timecounter other AM then i8254, you can release i8254 from those duties to allow using it as AM one-shot setting

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-15 Thread Lev Serebryakov
Hello, Alexander. You wrote 15 августа 2012 г., 15:19:32: AM I've meant `kern.timecounter`. kern.timecounter.tick: 1 kern.timecounter.choice: TSC(800) i8254(0) dummy(-100) kern.timecounter.hardware: TSC kern.timecounter.stepwarnings: 0 kern.timecounter.tc.i8254.mask: 65535

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-15 Thread Ian FREISLICH
Lev Serebryakov wrote: Hello, Lev. You wrote 15 =D0=B0=D0=B2=D0=B3=D1=83=D1=81=D1=82=D0=B0 2012 =D0=B3., 0:45:= 42: LS Answer looks trivial: router CPU is bottleneck. But here is one additi= onal LS detail: `top' never shows less than 50% of idle when torrents are LS active. And `idle'

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-15 Thread Alexander Motin
On 15.08.2012 14:23, Lev Serebryakov wrote: Hello, Alexander. You wrote 15 августа 2012 г., 15:19:32: AM I've meant `kern.timecounter`. kern.timecounter.tick: 1 kern.timecounter.choice: TSC(800) i8254(0) dummy(-100) kern.timecounter.hardware: TSC kern.timecounter.stepwarnings: 0

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-14 Thread Adrian Chadd
Hi, Would you be willing to compile a kernel with KTR so you can capture some KTR scheduler dumps? That way the scheduler peeps can feed this into schedgraph.py (and you can too!) to figure out what's going on. Maybe things aren't being scheduled correctly and the added latency is killing

Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

2012-08-14 Thread Doug Barton
On 08/14/2012 12:20 PM, Adrian Chadd wrote: Hi, Would you be willing to compile a kernel with KTR so you can capture some KTR scheduler dumps? That way the scheduler peeps can feed this into schedgraph.py (and you can too!) to figure out what's going on. Maybe things aren't being