I have 150-200 customers, each with their own simple queues.
I have an uplink to the ISP at 100/100 Mbps.
In the beginning, I could get up to 38 Mbps per. customer.
But now I can not get more than 20 Mbps per. customer.
All my clients have an IP address directly to the grid. 91.207.XXX.XXX which will put an queues on.
Are there any of you who can explain to me how it can be I lose 18 Mbps with simple queues. And I can not get more than 38 Mbps when I know there is about 92 Mbps between my PtP
We are having issues with simple queues only when the traffic is over 10M. We have thousands of customers using simple queues under 5M plans and they all works perfect. If we setup a customer for a 30M download and 5M upload. The customer can only do 1 concurrent connection at 17M and get there full 5M upload. If we disable the simple queue I am able to get 93M/87M speedtest. If I set the same shaping up with advanced queue and packet marking then everything works as expected.
We have noticed though that if we have the customer shaped to 30M with a simple queue they can
Download ISO at 10M
Download exe file at 10M
and still get 10M on speedtest for a total of 30M traffic on simple queue.
What we are seeing is that we are unable to get 1 concurrent tcp connection on a simple queue to go past 10M reliably. They can get a total of 30M but needs to have it coming from different streams. If we take off the simple queue with no other changes everything works perfect.
We have found a way around this but would prefer to shape all customers the same.
I just learned that if you change your Queue Type to ethernet-default that this would take care of you speed limits in the simple queue. We have done this in our test lap and so far has worked. We will be putting in our network tomorrow for live testing.
set
queue=ethernet-default/ethernet-default
by default is sets queue=default-small/default-small
which is too inaccurate with greater speeds
Change your simple queue under the advanced tab. There is a section in there called QueueType. By default this is set to default-small. Change the upload and download to ethernet-default.
/queue simple set numbers=0 queue=ethernet-default
Change the pfifo limit for the default-small to 50 (Going to try this today in live enviroment but have not done so yet)
The default pfifo-limit for the default-small is 10. We are looking at just changing this to 50 as then all our dynamic queues will be generated correctly for the package speed. I am not sure if this will affect lower package speeds yet but will post after I have my testing done on our network.
Let me know for questions or if I didn’t explain clearly.
If you disable simple queues you can get 38M to customers but soon as you enable them you only get 20M.
This was the issue we were seeing and I want to make sure I am trying to help with the same problem.
Also for testing purposes, you can try using an advance queue to make sure its the simple queue having the issues.
To do this create a Mangle rule for the ip address you want to shape and mark the packet
Then create a queue in the queue tree for that packet mark. You will need to do upload and download separately.
When doing these test I could shape to 100M/100M and get full package speed. But on simple que shaped to 100M/100M I could only get 18M until I changed the pfifo to 100. Now you may not need to go clear to 100 for the pfifo but that is where I am starting my testing as I do have single customers with 100M/100M plans.