> > I suppose the drop you see is CPU bound ? Did you profiled it > > again ? > > No, CPU is about times more in idle state in htb3, and > 5x lowest data rate. AFAIK, htb3 scheduler is faster, so that is the > reason of moving to htb3. ok then it is config issue probably. you should pin it down to smallest possible number of classes for test (say up to 5 classes) and then use tc -s show class ... to see internal statistics. Look for classes with small (or negative) tokens or ctokens - these are in throttling state and are slowing throughtput - then think if it is ok .. >From data you send one can't decide what's bad. In any case and as I said before, behavioue changed a bit so that results can be a bit different a may need tc script changes. devik _______________________________________________ LARTC mailing list / LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
