- From: "Liran Ma@OU" <lrma AT ou.edu>
- To: sridhar <dsridhar18 AT yahoo.com>
- Cc: discussion AT sctp.de
- Subject: Re: [SCTP-Discussion] problem with increasing CWND variable
- Date: Thu Apr 1 21:52:03 2004
- List-id: SCTP Discussions <discussion.sctp.de>
- Organization: University of Oklahoma
For each SCTP session, the receiver will notify the sender its receiver
buffer when the session is being setup. Therefore, the initial receiver
buffer size is fixed for each single simulation. After session setup, the
data sender will calculate the most recently receiver window of its peer,
which gives the sender an indication of the space available in the
receiver's inbound buffer.
In my point of view, if you kept the receiver buffer as 131026 you should
get the same throughput for all the link capacities given other parameters
are the same. Could you try multiple sessions instead of only one session to
measure the SCTP throughput if you want to use the fixed receiver buffer?
Liran
----- Original Message -----
From: "sridhar"
<dsridhar18 AT yahoo.com>
To: "Liran Ma@OU"
<lrma AT ou.edu>
Sent: Thursday, April 01, 2004 12:21 PM
Subject: Re: [SCTP-Discussion] problem with increasing CWND variable
>
>
>
So Is there a way to overcome this problem?. May be I
>
can increase the initial receiver window size. But
>
when I am increasing the receiver window I am running
>
out of space. I am measuring the SCTP throughput for
>
different link capacities like 100Mbps, 200Mbps,
>
300Mbps....1000Mbps..... SO every time do I need to
>
increase the receiver window according to the link
>
capacity? If I kept the initial receiver window at
>
131026 I am getting the same throughput for all the
>
link capacities. How should I solve this problem? Will
>
the value of the initial receiver window be the value
>
of receiver through out the simulation time? Then why
>
did they specify it as initial receiver window?
>
>
Thanks,
>
Sridhar!!
>
>
>
>
>
--- "Liran Ma@OU"
>
<lrma AT ou.edu>
>
wrote:
>
> It's because you limit the receiver window. As we
>
> know, the CWND can grow
>
> only when the current congestion window is being
>
> fully utilized. However, at
>
> any given time, the data sender MUST NOT transmit
>
> new data to any
>
> destination transport address if its peer's receiver
>
> window indicates that
>
> the peer has no buffer space (i.e. receiver window
>
> is 0, see RFC 2960).
>
> Therefore, when CNWD reaches the value of the
>
> receiver window, it won't be
>
> able to grow any more.
>
>
>
>
>
>
>
> ----- Original Message -----
>
> From: "sridharareddy duggireddy"
>
> <dsridhar18 AT yahoo.com>
>
> To:
>
> <discussion AT sctp.de>
>
> Sent: Thursday, April 01, 2004 9:05 AM
>
> Subject: [SCTP-Discussion] problem with increasing
>
> CWND variable
>
>
>
>
>
> > Hi,
>
> >
>
> > I have written a tcl script to measure the
>
> > throughput of SCTP protocol. In that script I have
>
> > specified the initial receiver window size as
>
> 131026
>
> > and initial ssthresh value as defaut value(65536).
>
> I
>
> > am using only one stream. When I ran the script
>
> and
>
> > looked at the trace file, the cwnd variable is
>
> > increasing until it reaches the value of initial
>
> > receiver window(131026) and then it is staying
>
> > constant for the remaining time. So the throughput
>
> is
>
> > not increasing even if I am increasing the link
>
> > capacity? May I know the reason for this?
>
> >
>
> > Thanks,
>
> > Sridhar!!
>
> >
>
> > __________________________________
>
> > Do you Yahoo!?
>
> > Yahoo! Small Business $15K Web Design Giveaway
>
> > http://promotions.yahoo.com/design_giveaway/
>
> > _______________________________________________
>
> > discussion mailing list
>
> > discussion AT sctp.de
>
> > http://www.sctp.de/mailman/listinfo/discussion
>
> >
>
>
>
> _______________________________________________
>
> discussion mailing list
>
> discussion AT sctp.de
>
> http://www.sctp.de/mailman/listinfo/discussion
>
>
>
__________________________________
>
Do you Yahoo!?
>
Yahoo! Small Business $15K Web Design Giveaway
>
http://promotions.yahoo.com/design_giveaway/
Archive powered by MHonArc 2.6.19+.