We are upgrading an existing application from Qnx2.21 to Qnx4.25C.
We are using TCPIP Socklet version 4.25H, Jul30,1999.
We ftp files from a WindowsOS to the Qnx4 computer in ascii mode.
I know binary is faster, but we must stay with the ascii mode to be backward
compatible.
From W98 using ftp from a DOS prompt in ascii mode:
A 307Kbyte ascii file takes about 200 seconds to put to the Qnx4
machine.
The same file put to the Qnx2 machine takes only 3.24 seconds.
Any ideas?
Have I forgot to configure something?
ms…
Anyone have any thoughts on this?
ms…
Mike Schneider <Mike.Schneider@us.heidelberg.com> wrote in message
news:8vb510$5vg$1@inn.qnx.com…
We are upgrading an existing application from Qnx2.21 to Qnx4.25C.
We are using TCPIP Socklet version 4.25H, Jul30,1999.
We ftp files from a WindowsOS to the Qnx4 computer in ascii mode.
I know binary is faster, but we must stay with the ascii mode to be
backward
compatible.
From W98 using ftp from a DOS prompt in ascii mode:
A 307Kbyte ascii file takes about 200 seconds to put to the Qnx4
machine.
The same file put to the Qnx2 machine takes only 3.24 seconds.
Any ideas?
Have I forgot to configure something?
ms…
I was able to reproduce this, the weirdest thing is the QNX4 machine
is running at 100% CPU utilisation (ftpd ~40% Proc32 60%)
This looks like a bug to me.
This is with Beta 5.0. QSSL.still time left for a fix ? 
“Mike Schneider” <Mike.Schneider@us.heidelberg.com> wrote in message
news:8vf3f0$965$1@inn.qnx.com…
Anyone have any thoughts on this?
ms…
Mike Schneider <> Mike.Schneider@us.heidelberg.com> > wrote in message
news:8vb510$5vg$> 1@inn.qnx.com> …
We are upgrading an existing application from Qnx2.21 to Qnx4.25C.
We are using TCPIP Socklet version 4.25H, Jul30,1999.
We ftp files from a WindowsOS to the Qnx4 computer in ascii mode.
I know binary is faster, but we must stay with the ascii mode to be
backward
compatible.
From W98 using ftp from a DOS prompt in ascii mode:
A 307Kbyte ascii file takes about 200 seconds to put to the Qnx4
machine.
The same file put to the Qnx2 machine takes only 3.24 seconds.
Any ideas?
Have I forgot to configure something?
ms…
\
I don’t see the cpu useage as you mention.
While the ascii mode ftp is occurring, our other applications seem to be
running normally.
If I slay all our applications the ftp is slightly faster, but not a
significant difference.
I did the same test with the 307Kbyte file between two Qnx4 machines, and
got similar times.
In ascii mode, 190 seconds, 1.58 Kbytes/sec.
In binary mode, 1.6 seconds, 185 Kbytes/sec.
What kind of times are you getting for ascii mode transfers?
Anyone out there getting good results for this kind of ftp?
ms…
Mario Charest <mcharest@void_zinformatic.com> wrote in message
news:8vf5nv$h5e$1@nntp.qnx.com…
I was able to reproduce this, the weirdest thing is the QNX4 machine
is running at 100% CPU utilisation (ftpd ~40% Proc32 60%)
This looks like a bug to me.
This is with Beta 5.0. QSSL.still time left for a fix ? >
Mike Schneider wrote in message
news:8vb510$5vg$> 1@inn.qnx.com> …
We are upgrading an existing application from Qnx2.21 to Qnx4.25C.
We are using TCPIP Socklet version 4.25H, Jul30,1999.
We ftp files from a WindowsOS to the Qnx4 computer in ascii mode.
I know binary is faster, but we must stay with the ascii mode to be
backward
compatible.
From W98 using ftp from a DOS prompt in ascii mode:
A 307Kbyte ascii file takes about 200 seconds to put to the Qnx4
machine.
The same file put to the Qnx2 machine takes only 3.24 seconds.
Any ideas?
Have I forgot to configure something?
ms…
Mario,
I did some more testing and got similar numbers for cpu time.
I slayed all my applications on both Qnx4 nodes, and ran sysmon.
The client did a put of the 307Kbyte file:
The ascii transfer time was 71 seconds, 4.26Kbytes/sec.
The binary transfer time was 1.3 seconds, 227Kbytes/sec.
While the transfer was occurring in ascii mode:
- client side showed useage by PID 00008 of 90+ percent.
- server side showed the same useage that you reported, about 40% ftpd
and 60% Proc32.
As soon as the ftp transfer is complete, the server side displays the same
useage as the client side.
QSSL comments/suggestions, or anyone?
ms…
Mario Charest <mcharest@void_zinformatic.com> wrote in message
news:8vf5nv$h5e$1@nntp.qnx.com…
I was able to reproduce this, the weirdest thing is the QNX4 machine
is running at 100% CPU utilisation (ftpd ~40% Proc32 60%)
This looks like a bug to me.
This is with Beta 5.0. QSSL.still time left for a fix ? >
Mike Schneider <> Mike.Schneider@us.heidelberg.com> > wrote in message
news:8vb510$5vg$> 1@inn.qnx.com> …
We are upgrading an existing application from Qnx2.21 to Qnx4.25C.
We are using TCPIP Socklet version 4.25H, Jul30,1999.
We ftp files from a WindowsOS to the Qnx4 computer in ascii mode.
I know binary is faster, but we must stay with the ascii mode to be
backward
compatible.
From W98 using ftp from a DOS prompt in ascii mode:
A 307Kbyte ascii file takes about 200 seconds to put to the Qnx4
machine.
The same file put to the Qnx2 machine takes only 3.24 seconds.
Any ideas?
Have I forgot to configure something?
ms…
“Mike Schneider” <Mike.Schneider@us.heidelberg.com> wrote in message
news:8vu1te$730$1@inn.qnx.com…
Mario,
I did some more testing and got similar numbers for cpu time.
I slayed all my applications on both Qnx4 nodes, and ran sysmon.
The client did a put of the 307Kbyte file:
The ascii transfer time was 71 seconds, 4.26Kbytes/sec.
In my case it was taking forever, I abort the transfer
The binary transfer time was 1.3 seconds, 227Kbytes/sec.
While the transfer was occurring in ascii mode:
- client side showed useage by PID 00008 of 90+ percent.
- server side showed the same useage that you reported, about 40% ftpd
and 60% Proc32.
As soon as the ftp transfer is complete, the server side displays the same
useage as the client side.
QSSL comments/suggestions, or anyone?
ms…
Mario Charest <mcharest@void_zinformatic.com> wrote in message
news:8vf5nv$h5e$> 1@nntp.qnx.com> …
I was able to reproduce this, the weirdest thing is the QNX4 machine
is running at 100% CPU utilisation (ftpd ~40% Proc32 60%)
This looks like a bug to me.
This is with Beta 5.0. QSSL.still time left for a fix ? >
Mike Schneider <> Mike.Schneider@us.heidelberg.com> > wrote in message
news:8vb510$5vg$> 1@inn.qnx.com> …
We are upgrading an existing application from Qnx2.21 to Qnx4.25C.
We are using TCPIP Socklet version 4.25H, Jul30,1999.
We ftp files from a WindowsOS to the Qnx4 computer in ascii mode.
I know binary is faster, but we must stay with the ascii mode to be
backward
compatible.
From W98 using ftp from a DOS prompt in ascii mode:
A 307Kbyte ascii file takes about 200 seconds to put to the Qnx4
machine.
The same file put to the Qnx2 machine takes only 3.24 seconds.
Any ideas?
Have I forgot to configure something?
ms…
There is a new version being worked on which seems to have solved
the problem. Which version it becomes part of is hard to say at this
time as more testing will need to be done.
Mario Charest <mcharest@void_zinformatic.com> wrote in message
I was able to reproduce this, the weirdest thing is the QNX4 machine
is running at 100% CPU utilisation (ftpd ~40% Proc32 60%)
This looks like a bug to me.
This is with Beta 5.0. QSSL.still time left for a fix ? >
Mike Schneider <> Mike.Schneider@us.heidelberg.com> > wrote in message
We are upgrading an existing application from Qnx2.21 to Qnx4.25C.
We are using TCPIP Socklet version 4.25H, Jul30,1999.
We ftp files from a WindowsOS to the Qnx4 computer in ascii mode.
I know binary is faster, but we must stay with the ascii mode to be
backward
compatible.
From W98 using ftp from a DOS prompt in ascii mode:
A 307Kbyte ascii file takes about 200 seconds to put to the Qnx4
machine.
The same file put to the Qnx2 machine takes only 3.24 seconds.