Some ideas - Remember that --threads and --cpu only take effect on the first click-install; after that need to click-uninstall before --threads and --cpu will matter
- Check /click/threads : are there really 2 threads? - Your thread assignment assumes bidirectional traffic, are you feeding traffic in both directions? Eddie Latency Buster wrote: >> You want --cpu=0 as it sets on which CPU to preferentially run the threads. >> So if you have two threads, then --cpu=0 would imply that you want cpu0 and >> cpu1. > I also did --cpu=0 but it does no good. All the time I see one kclick > in 'S' state. > I have a 4 CPU machine. So, even if I did --cpu=2, then it would mean > that the threads would run on cpu2 and cpu3.. > _______________________________________________ > click mailing list > [email protected] > https://amsterdam.lcs.mit.edu/mailman/listinfo/click _______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click
