> Angus, could you share the upload script on your server?
It's not a script, the server uses the ICS web application server
component, and the upload page is Delphi code, based on the upload demo
page in the ICS web server sample.
Angus
--
To unsubscribe or change your settings for TWSocket
Angus, could you share the upload script on your server?
On Thu, May 12, 2016 at 5:35 PM, RTT wrote:
>
>
> Either way, if the problem is the async nature of ICS,
>> shouldn't an alternate method be provided?
>>
>
> Try with the TransmitFile function
>
>
Either way, if the problem is the async nature of ICS,
shouldn't an alternate method be provided?
Try with the TransmitFile function
https://msdn.microsoft.com/en-us/library/windows/desktop/ms740565(v=vs.85).aspx
You may create a descendant of the THttpCli, override the SocketDataSent
On Thu, May 12, 2016 at 4:24 PM, RTT wrote:
>
> If that's the case, using SYN, that is sync, to compare against the async
> ICS is not of any help. You need to compare with another async component.
I think all other libraries are blocking, Indy, Synapse, Delphi's own
tcp/ip
Checked again just now, w7:
ICS with 64k buffer: Upload Duration: 33.2 secs / Speed: 137,151 chars/sec
SYN: Upload Duration: 2 secs / Speed: 2,275,855 chars/sec
On Thu, May 12, 2016 at 4:04 PM, brian - wrote:
> Erm, I thought we all reached a clear conclusion that the
GET seems fine though. You mentioned changing the buffer size, where would
you do that? I tried changing 8k to 64k in OverbyteIcsHttpProt.pas here,
but it made no difference:
~4617
procedure THttpCli.SocketDataSent(Sender : TObject; ErrCode : Word);
var
Len : Integer;
begin
if not
Note that the original subject is a bit misleading, the issue is not about
ssl POST, but POST in general, whether on http or https.
On Thu, May 12, 2016 at 12:13 PM, Angus Robertson - Magenta Systems Ltd <
an...@magsys.co.uk> wrote:
> > I still have some Windows 7 VMs, so will do more testing
Here we go,
*98 SE (Delphi7/v5)* VM
ICS: Upload Duration: 34.67 secs/Speed: 131,341 chars/sec
SYN: Upload Duration: 9.05 secs/Speed: 503,314 chars/sec
*2000* VM
ICS: Upload Duration: 34.38 secs/Speed: 132,475 chars/sec
SYN: Upload Duration: 4.67 secs/Speed: 974,531 chars/sec
*XP* VM
ICS:
On 27/04/2016 18:12, Angus Robertson - Magenta Systems Ltd wrote:
WinInet is a special case and probably handles TCP/IP as a driver or
something we can not do.
Maybe similar performance can be achieved with the Winsock TransmitFile
and TransmitPackets functions.
--
To unsubscribe or change
I am assuming that you do not have the QOS Packet Scheduler service
installed (under Local Area Connection Properties for the LAN adapter) -
this has always screwed things up for me over the years.
Regards,
Tim
-Original Message-
From: TWSocket
On Wed, Apr 27, 2016 at 8:46 PM, brian - wrote:
>
>
>> I still have some Windows 7 VMs, so will do more testing next week,
>> once the new OpenSSL stuff is finished.
>>
>
>
> These tests on VMs are flawed though, as observed in all my testing,
> should be done on a real W7
On Wed, Apr 27, 2016 at 8:28 PM, Angus Robertson - Magenta Systems Ltd <
an...@magsys.co.uk> wrote:
>
> I still have some Windows 7 VMs, so will do more testing next week,
> once the new OpenSSL stuff is finished.
>
These tests on VMs are flawed though, as observed in all my testing, should
be
On 27/04/2016 18:12, Angus Robertson - Magenta Systems Ltd wrote:
Does not really make sense to me, but could be down to improved async
winsock with Windows 10.
Maybe related?
https://blogs.windows.com/buildingapps/2015/07/02/networking-api-improvements-in-windows-10/
--
To unsubscribe or
> ** Fresh Win7 on my PC: *
> - ICS: Upload Duration: 34.39 secs/132,417 chars/sec
> - SYN: Upload Duration: 2.03 secs/Speed: 2,241,135 chars/sec
>
> ** Fresh Win10 on my PC**
> - ICS: Upload Duration: 1.88 secs/ 2,427,498 chars/sec
> - SYN: Upload Duration: 2.02 secs/Speed: 2,257,802 chars/sec
Alright I'm back with some interesting results that confirm my suspicions
(actually meant 300/30 Mbit btw)
* All VM tests (xp/w7/w10/ubuntu) showed similar results around 0.9..1MB/s
upload, except when using a UK VPN: ICS was again slow.
* Win XP on a netbook on wifi (Asus eee901): ICS: 65.8s.
Yeah, I'm on 100/30 Mbit fiber, Windows 7 x64 and the latest V8 SVN with
Delphi Seattle. Some days ago I tried an old V5 with Delphi7 to rule out
this problem having been recently introduced, but I observed the same
results. Since you mentioned Windows 10, I thought of making a few extra
tests
> Memo isn't touched during the progress, only the progressbar.
> Removed OnSenData event, same results.
You appear to be on a Spanish RIMA (Red IP Multi Acceso) network,
although trace route does not complete.
Trace Route to: 83.39.166.229
Can Not Ping Host (83.39.166.229) : Request timed
of the freeware Internet Component Suite (ICS)
http://www.overbyte.be
-Message d'origine-
De : TWSocket [mailto:twsocket-boun...@lists.elists.org] De la part de brian
-
Envoyé : mardi 26 avril 2016 03:58
À : ICS support mailing
Objet : Re: [twsocket] SSL post extremely slow
Did the test with a 4,5MB
On 25/04/2016 18:12, Angus Robertson - Magenta Systems Ltd wrote:
Done some testing with a view to investigating this issue, but not
currently sure it's worth any more time.
How about testing against a non-ICS server.
https://posttestserver.com/
https://httpbin.org/
http://putsreq.com/
--
To
> Are there any known issues with SslHttpCli for sending data? I've
> observed the following:
> Sending a 3MB picture to imgur:
> * with ICS/OpenSSL: takes ~27 seconds
Done some testing with a view to investigating this issue, but not
currently sure it's worth any more time.
I'm using an
You never mentioned you were testing the synchronous methods of the
component, that is not a fair test of ICS performance, you should be
using proper events and the async component methods.
I'm observing the same issue with async calls though, did the same test
from above but this time with
> Captured with Microsoft Network Monitor, non-SSL post to my
> server:
> Synapse: 3.8s http://pasted.co/1f69a8a8
> ICS: 46.5s
All these measurements have little value when you are not comparing
like with like.
After my last message, I assume you have redesigned your ICS
application to use
Captured with Microsoft Network Monitor, non-SSL post to my server:
Synapse: 3.8s http://pasted.co/1f69a8a8
ICS: 46.5s
https://mega.nz/#!b05jyRzT!hLB8_xKHeHJyRb7nAXcQDM2mv0_RW9uf4y-iN3e6gkc (too
large for text paste sites)
few lines from each:
Frame, time, time offset, process, source,
> I think the main issue lies on OverbyteIcsHttpProt around
>
> while FState <> httpReady do begin
> > {$IFDEF MSWINDOWS}
> > if MsgWaitForMultipleObjects(0, Pointer(nil)^, FALSE,
> > 1000, QS_ALLINPUT) = WAIT_OBJECT_0 then
> > {$ENDIF}
> > MessagePump;
You never mentioned you were
> Do you think there might be an easy solution to this coming soon?
> the problem is pretty serious,
I would disagree this a serious problem, it might be annoying that your
ICS implementation runs slower than some other applications, but it's
hardly a major show stopper.
HTTP was never
Some more tests (modified buffer size for the 2nd test)
ICS: ~23s, 377 x 8KB, 55-60ms between packets: http://pastebin.com/Uq5mphUH
ICS @ 64KB: ~22s, 48 x 64KB, 450-470ms between packets:
http://pastebin.com/wTat71Qe
SYN: ~6s, 49 x 64KB, 110-120ms between packets: http://pastebin.com/g5svt11P
> I updated the FTP client buffers to 32K several years ago for better
performance.
Yep this was 2011 and it made a huge difference for me.
http://marc.info/?l=twsocket=131146591403948=2
And your response:
Log:
- Added published property DataSocketSndBufSize and public property
+27(41) 373 0529
> Fax: +27(86) 650 0135
> Disclaimer
>
> > -Original Message-
> > From: TWSocket [mailto:twsocket-boun...@lists.elists.org] On Behalf Of
> brian
> > -
> > Sent: 14 April 2016 00:26
> > To: ICS support mailing
> > Subject: Re:
> Are there any known issues with SslHttpCli for sending data?
It seems the component still uses 8K buffers for receiving and sending
data, which was fine 15 years ago when we used slow modems and 10Mb
ethernet, but larger buffers would be more efficient with current
internet speeds.
I
Synapse (OpenSSL) ~7 seconds.
On Wed, Apr 13, 2016 at 2:07 AM, brian - wrote:
> Update: sending through WinInet in my project: 6-7 seconds. What could be
> the issue with ICS?
>
> On Wed, Apr 13, 2016 at 12:47 AM, brian - wrote:
>
>> Are there any
Update: sending through WinInet in my project: 6-7 seconds. What could be
the issue with ICS?
On Wed, Apr 13, 2016 at 12:47 AM, brian - wrote:
> Are there any known issues with SslHttpCli for sending data? I've observed
> the following:
>
> Sending a 3MB picture to imgur:
Are there any known issues with SslHttpCli for sending data? I've observed
the following:
Sending a 3MB picture to imgur:
* with ICS/OpenSSL: takes ~27 seconds
* with Indy/OpenSSL: 8-10 seconds (didn't send correctly though so can't
confirm 100%, but the post part did take that long nonetheless)
32 matches
Mail list logo