newsgroups-index (beta)

Current group: bit.listserv.vse-l

Poor performance on TCP/IP for VSE

Poor performance on TCP/IP for VSE  
Naval Espasa
 Re: Poor performance on TCP/IP for VSE  
The Family
 Re: Poor performance on TCP/IP for VSE  
John Rankin
 Re: Poor performance on TCP/IP for VSE  
Naval Espasa
From:Naval Espasa
Subject:Poor performance on TCP/IP for VSE
Date:19 Jan 2005 10:02:38 -0800
This is a multi-part message in MIME format.

------=_NextPart_000_0042_01C4FE57.C510D100
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset="Windows-1252"


We have installed VSE/ESA 2.6.2, Mq-Series 2.1.2 and TCP/IP for VSE 1.5.

I use MQ-Series for sending messages another site, but only I can send a =
few messages per second,
because TCP/IP stack doesn't send next message until ACKs related to the =
send is received from
the peer.=20

I think that TCP/IP stack should transmit all the data allowed within a =
foreign window definition, without=20
to have to wait for ACKs by each message sent.

Any ideas how can I resolve this?

Naval Espasa
Barcelona Stock Exchange


------=_NextPart_000_0042_01C4FE57.C510D100
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset="Windows-1252"



charset=3Dwindows-1252">




 

We have installed VSE/ESA 2.6.2, Mq-Series 2.1.2 and =
TCP/IP=20
for VSE 1.5.

 

I use MQ-Series for sending messages another site, =
but only I=20
can send a few messages per second,

because TCP/IP stack doesn't send next message until =
ACKs=20
related to the send is received from

the peer.

 

I think that TCP/IP stack should transmit all the =
data allowed=20
within a foreign window definition, without

to have to wait for ACKs by each message=20
sent.

 

Any ideas how can I resolve this?

 

Naval Espasa

Barcelona Stock Exchange

 

 


------=_NextPart_000_0042_01C4FE57.C510D100--
From:The Family
Subject:Re: Poor performance on TCP/IP for VSE
Date:Wed, 19 Jan 2005 18:31:05 GMT

UDP


"Naval Espasa" wrote in message
news:004501c4fe4f$635a99d0$0301100a@NAVAL...

We have installed VSE/ESA 2.6.2, Mq-Series 2.1.2 and TCP/IP for VSE 1.5.

I use MQ-Series for sending messages another site, but only I can send a few
messages per second,
because TCP/IP stack doesn't send next message until ACKs related to the
send is received from
the peer.

I think that TCP/IP stack should transmit all the data allowed within a
foreign window definition, without
to have to wait for ACKs by each message sent.

Any ideas how can I resolve this?

Naval Espasa
Barcelona Stock Exchange
From:John Rankin
Subject:Re: Poor performance on TCP/IP for VSE
Date:19 Jan 2005 14:35:29 -0800
> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3189000878_5806889
Content-type: text/plain;
charset="US-ASCII"
Content-transfer-encoding: 7bit

On 1/19/05 12:50 PM, "Naval Espasa" wrote:

> We have installed VSE/ESA 2.6.2, Mq-Series 2.1.2 and TCP/IP for VSE 1.5.
>
> I use MQ-Series for sending messages another site, but only I can send a few
> messages per second,
> because TCP/IP stack doesn't send next message until ACKs related to the send
> is received from
> the peer.
>
> I think that TCP/IP stack should transmit all the data allowed within a
> foreign window definition, without
> to have to wait for ACKs by each message sent.
>
> Any ideas how can I resolve this?
>
> Naval Espasa
> Barcelona Stock Exchange

Naval,

This is not an issue of TCP/IP. TCP/IP for VSE 1.5 can queue and
process an extremely large amount of information, without waiting for it to
be ACKed. However, each specific application send, must be tied to a
response in order to provide proper error reporting information, otherwise,
the originating application may never know that the data was lost or failed
in its transmission. TCP/IP for VSE 1.5 allows applications to queue a
large number of concurrent requests along these lines and provides several
different methods of implement this queuing. However, MQ-Series choose to
use none of the provided techniques and implemented their send operation in
the simplest possible way. This has created the performance problem of
which you speak. Even so, our development staff has worked out a system
that will allow, simplistically written applications, to improve their
performance. This enhancement is still being tested and will be made
available within the base product as soon possible.

John Rankin
President
CSI International
(800) 795-4914
(740) 420-5400
WWW.e-VSE.com


--B_3189000878_5806889
Content-type: text/html;
charset="US-ASCII"
Content-transfer-encoding: quoted-printable



Re: Poor performance on TCP/IP for VSE


On 1/=
19/05 12:50 PM, "Naval Espasa" <nespasa@borsabcn.es> wrote:<=
BR>


E=3D'font-size:12.0px'>We have installed VSE/ESA 2.6.2, Mq-Series 2.1.2 and TC=
P/IP for VSE 1.5.

 

I use MQ-Series for sending messages another site, but only I can send a fe=
w messages per second,

because TCP/IP stack doesn't send next message until ACKs related to the se=
nd is received from

the peer.

 

I think that TCP/IP stack should transmit all the data allowed within a for=
eign window definition, without

to have to wait for ACKs by each message sent.

 

Any ideas how can I resolve this?

 

Naval Espasa

Barcelona Stock Exchange

LE=3D'font-size:12.0px'>

Naval,



    This is not an issue of TCP/IP.  TCP/IP for VS=
E 1.5 can queue and process an extremely large amount of information, withou=
t waiting for it to be ACKed.  However, each specific application send,=
must be tied to a response in order to provide proper error reporting infor=
mation, otherwise, the originating application may never know that the data =
was lost or failed in its transmission.  TCP/IP for VSE 1.5 allows appl=
ications to queue a large number of concurrent requests along these lines an=
d provides several different methods of implement this queuing.  Howeve=
r, MQ-Series choose to use none of the provided techniques and implemented t=
heir send operation in the simplest possible way.  This has created the=
performance problem of which you speak.  Even so, our development staf=
f has worked out a system that will allow, simplistically written applicatio=
ns, to improve their performance.  This enhancement is still being test=
ed and will be made available within the base product as soon possible.



John Rankin

President

CSI International

(800) 795-4914

(740) 420-5400

WWW.e-VSE.com






--B_3189000878_5806889--
From:Naval Espasa
Subject:Re: Poor performance on TCP/IP for VSE
Date:20 Jan 2005 01:34:10 -0800
This is a multi-part message in MIME format.

------=_NextPart_000_007F_01C4FEDB.5A83B350
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset="iso-8859-1"

Re: Poor performance on TCP/IP for VSEJohn,

Thanks so much for your response. I'm very happy that your =
development staff has worked to resolve this problem.
Could you give me a date? For me is very urgent to improve this =
communication. =20

Also I have a COBOL TCP/IP program for sending and receiving =
files that suffers same problem. Could you show me the several =
differents methods of implement this queuing?.

Thanks.


Naval Espasa

Barcelona Stock Exchange


=20








From: John Rankin=20
To: VSE Discussion List=20
Sent: Wednesday, January 19, 2005 11:34 PM
Subject: Re: Poor performance on TCP/IP for VSE


On 1/19/05 12:50 PM, "Naval Espasa" wrote:


We have installed VSE/ESA 2.6.2, Mq-Series 2.1.2 and TCP/IP for VSE =
1.5.
=20
I use MQ-Series for sending messages another site, but only I can =
send a few messages per second,
because TCP/IP stack doesn't send next message until ACKs related to =
the send is received from
the peer.=20
=20
I think that TCP/IP stack should transmit all the data allowed =
within a foreign window definition, without=20
to have to wait for ACKs by each message sent.
=20
Any ideas how can I resolve this?
=20
Naval Espasa
Barcelona Stock Exchange


Naval,

This is not an issue of TCP/IP. TCP/IP for VSE 1.5 can queue and =
process an extremely large amount of information, without waiting for it =
to be ACKed. However, each specific application send, must be tied to a =
response in order to provide proper error reporting information, =
otherwise, the originating application may never know that the data was =
lost or failed in its transmission. TCP/IP for VSE 1.5 allows =
applications to queue a large number of concurrent requests along these =
lines and provides several different methods of implement this queuing. =
However, MQ-Series choose to use none of the provided techniques and =
implemented their send operation in the simplest possible way. This has =
created the performance problem of which you speak. Even so, our =
development staff has worked out a system that will allow, =
simplistically written applications, to improve their performance. This =
enhancement is still being tested and will be made available within the =
base product as soon possible.

John Rankin
President
CSI International
(800) 795-4914
(740) 420-5400
WWW.e-VSE.com

------=_NextPart_000_007F_01C4FEDB.5A83B350
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset="iso-8859-1"


Re: Poor performance on TCP/IP for VSE
charset=3Diso-8859-1">




John,

 

        Thanks so =
much for=20
your response. I'm very happy that your development staff has worked to =
resolve=20
this problem.

Could you give me a date? For me is very urgent =
to=20
improve this communication.   

 

size=3D2>        Also I =
; have=20
a COBOL TCP/IP  program for sending and =
receiving=20
files that suffers same problem. Could you show me the several =
differents=20
methods of implement this queuing?.

 

Thanks.

 

 

Naval Espasa

 

Barcelona Stock Exchange

 

 

 

 

 

 

 

 

 

 

 


style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">

Sent: Wednesday, January 19, =
2005 11:34=20
PM

Subject: Re: Poor performance =
on TCP/IP=20
for VSE


style=3D"FONT-SIZE: 12px">On 1/19/05 12:50 PM, "Naval Espasa" < href=3D"mailto:nespasa@borsabcn.es">nespasa@borsabcn.es>=20
wrote:


style=3D"FONT-SIZE: 12px">We have installed VSE/ESA 2.6.2, Mq-Series =
2.1.2 and=20
TCP/IP for VSE 1.5.
 
I use MQ-Series for sending =
messages=20
another site, but only I can send a few messages per =
second,
because=20
TCP/IP stack doesn't send next message until ACKs related to the =
send is=20
received from
the peer.
 
I think that TCP/IP stack =
should=20
transmit all the data allowed within a foreign window definition, =
without=20

to have to wait for ACKs by each message sent.
 
Any =
ideas=20
how can I resolve this?
 
Naval Espasa
Barcelona Stock =

Exchange
face=3D"Verdana, Helvetica, Arial"> style=3D"FONT-SIZE: =
12px">
Naval,

    This is not=20
an issue of TCP/IP.  TCP/IP for VSE 1.5 can queue and process an=20
extremely large amount of information, without waiting for it to be =
ACKed.=20
 However, each specific application send, must be tied to a =
response in=20
order to provide proper error reporting information, otherwise, the=20
originating application may never know that the data was lost or =
failed in its=20
transmission.  TCP/IP for VSE 1.5 allows applications to queue a =
large=20
number of concurrent requests along these lines and provides several =
different=20
methods of implement this queuing.  However, MQ-Series choose to =
use none=20
of the provided techniques and implemented their send operation in the =

simplest possible way.  This has created the performance problem =
of which=20
you speak.  Even so, our development staff has worked out a =
system that=20
will allow, simplistically written applications, to improve their =
performance.=20
 This enhancement is still being tested and will be made =
available within=20
the base product as soon possible.

John =
Rankin
President
CSI=20
International
(800) 795-4914
(740)=20
420-5400
WWW.e-VSE.com


------=_NextPart_000_007F_01C4FEDB.5A83B350--
   
Copyright © 2006 newsgroups-index   -   All rights reserved   -   Impressum