Airplane777
join:2004-06-20
4 edits | reply to cmaenginsb
Re: Monowall general Traffic Shaper queue approaches ?
Hi cmaenginsb:
Thanks for your post.
I know that you, DaSneaky, Lutful, SuperDog, and others here are on really on top of this stuff, so I thought I'd put this thread forward to see if it will help me see the best way to do my queues.
You may have hit the nail on the head for me when you said, "At the end of the day, just like radio choice your choice in traffic shaping is going to reflect your business ideas." Maybe my question should have been:
Queueing choices vs business ideas ?
I too plan to rate limit my customers. I will be using an ADSL line.
You said, "...it's cheap to have a high capacity network (with the exception of the upstream)". By "cheap" do you mean something similiar to what DaSneaky1D said?
DaSneaky1D said, "...download is considered a "low cost" connection...which means that over utilization of it is less likely compared to the upload, so there is no gain or loss to doing shaping for download."
Do both of you mean that since there is so much download BW, that all that download BW probably won't hinder the incoming data, and thus there is no need to even try to have a queue for incoming data packets. That is queueing won't help incoming data at all (as long as the incoming data isn't congested).
Are both of you saying (in slightly different words) that since download is so much higher BW then the upload BW, that the high download BW doesn't need priortization of data? Or IOW, if a WISP is offering high enough BW on the download side, that incoming data won't be hindered as the incoming data is going on to our WISP customers? And since the incoming data won't be hindered (no matter in which order it is coming in at), that this incoming data will travel to a WISP customer unhindered and unblocked. Did I say that right?
But since the upload BW is so much lower in an ADSL circuit, I should do queues for the uploaded data because if uploaded data isn't handeled efficiently (since the upload BW is so low), improperly handeled upload data could affect proper downloading of data?
Upload que of ACK: ACK data should be queued to be sent out with high priority, so that the server that is downloading data to us, will know very quickly that we have received that servers data. Do I have that right?
Upload queue of DNS: And DNS upload should have high priority, in order for people who are browsing to have quick downloads when they browse using their browser.
Upload queue of VoIP and IP video: And maybe VoIP and IP video on the upload side should be queued for high priority, since it is so time sensitive and we are able to control that. VoIP is two way, but I imagine IP video is mainly just one way.
All other upload: I assume I would make everything else low priority, which would include all P2P. Am I correct in thinking that I don't have to worry too much about P2P download?
With all that said, I'm still wondering if we should consider queueing for incoming data due to the oversubscription we do. We have to do oversubscription to make a profit so we do oversubscription and the incoming data probably could get congested at times. That makes me think that maybe we WISPs should be doing queueing on incoming data, just because we do oversubscription, which will congest incoming data.
It would be great to hear how other WISPs approach their queueing. |
