From: Maciej Soltysiak <maciej@soltysiak.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] How to address IT Pros to the issue?
Date: Thu, 13 Dec 2012 17:28:07 +0100 [thread overview]
Message-ID: <CAMZR1YBsRch6JpFSv-+S_Av=nUN+h8WeLggu2H4PLzok0O68cA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
Hello,
Real Example #1:
"We have a 5Mbps CIFS partition and XXX was saturating it so no one could
print, use office applications (e.g. Word would hang trying to get printer
parameters across the network), network shares, anything that uses CIFS
basically. We asked the network profiling guys to investigate and they came
back with XXX as the culprit."
Basically here they had an application that saturated the whole 5 Mbps of
their Class of Service - The XXX application was made the root-cause, not
how the queues were utilized.
Real Example #2:
Introduction of XXX application to "Reduce bandwidth utilization, typically
by 60-95 percent, across all TCP-based applications. Free up bandwidth for
other applications, like VoIP or Citrix, so they can perform better."
Here the problems for VoIP and Citrix are perceived in bandwidth, so
instead of working to reduce latency, they implement TCP mangling gizmos to
compress/coalesce/whatever traffic to reduce bandwidth used. Probably the
good result they are having is not due to bandwidth use reduced but simply
from the amount of packets on wire and less to manage on the droptail
queues.
These 2 examples are real world IT Pros talking. Enterprise might be a huge
pain to debloat!
Regards,
Maciej
[-- Attachment #2: Type: text/html, Size: 7009 bytes --]
reply other threads:[~2012-12-13 16:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMZR1YBsRch6JpFSv-+S_Av=nUN+h8WeLggu2H4PLzok0O68cA@mail.gmail.com' \
--to=maciej@soltysiak.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox