Hello, I did experiments on Windows, and results are much more better, in case of WS call only 181 milliseconds are spent to startup/shutdown:
C:\conclient\bin\Debug>timeit conclient.exe echo "This is echo test which actual ly is sent to Web Service" 09.12.2009 00:40:02.053:Starting up This is echo test which actually is sent to Web Service 09.12.2009 00:40:02.734:Shutdown - took 680 millis Version Number: Windows NT 5.1 (Build 2600) Exit Time: 0:40 am, Saturday, September 12 2009 Elapsed Time: 0:00:00.861 Process Time: 0:00:00.440 System Calls: 17699 Context Switches: 1282 Page Faults: 6649 Bytes Read: 1225767 Bytes Written: 91594 Bytes Other: 361753 C:\conclient\bin\Debug>timeit conclient.exe 09.12.2009 00:40:29.212:Starting up SiloFX connector, (c) 2008 SiloDEV Username in env "SXUSER", Password in env "SXPASS" Usage [-m<module>] [-c<class>] command 09.12.2009 00:40:29.223:Shutdown - took 20 millis Version Number: Windows NT 5.1 (Build 2600) Exit Time: 0:40 am, Saturday, September 12 2009 Elapsed Time: 0:00:00.180 Process Time: 0:00:00.130 System Calls: 5112 Context Switches: 328 Page Faults: 1845 Bytes Read: 110345 Bytes Written: 0 Bytes Other: 127610 So it looks indeed that there is some kind of problem with mono. Can you please look on it? Thanks, Madars On Fri, Sep 11, 2009 at 11:21 PM, Madars Vitolins <[email protected] > wrote: > Dear list, > I have problem with simple command line binary which calls web service once > at it's execution time. Its primary purpose is to execute web service once, > return result to standard output and shutdown i.e. return. Problem is that > for some reason if Web Service was executed in takes about about 1.5 second > for binary to shut down. If Web Service was not executed, then shutdown time > is OK (28 milliseconds). > > Where could be problem, how can I reduce that shutdown time? I have already > tried to turn off keep a live for WS connections, but result is the same. I > am using this tool as command line access to web system, and if I am > utilizing this client in scripts, then it makes those scripts long running. > Here is some benchmark. Time markers I have added at the very beginning and > before return command. > > If invoking WS, then return takes long: > > $ time mono conclient.exe echo "This is echo test which actually is sent to > Web Service" > 09.11.2009 23:20:16.508:Starting up > This is echo test which actually is sent to Web Service > 09.11.2009 23:20:16.808:Shutdown - took 321 millis > > real 0m1.814s > user 0m0.296s > sys 0m0.024s > > Processing took 321 milliseconds, but overall it took almost 2 seconds. > > Here is timing when there is not WS invoked: > > $ time mono conclient.exe > 09.11.2009 23:20:34.047:Starting up > SiloFX connector, (c) 2008 SiloDEV > Username in env "SXUSER", Password in env "SXPASS" > Usage [-m<module>] [-c<class>] command > 09.11.2009 23:20:34.060:Shutdown - took 25 millis > > real 0m0.055s > user 0m0.048s > sys 0m0.004s > > > Program is written in C# > $ mono --version > Mono JIT compiler version 2.4.2 (tarball Tue Jun 23 16:32:12 EEST 2009) > Copyright (C) 2002-2008 Novell, Inc and Contributors. www.mono-project.com > TLS: __thread > GC: Included Boehm (with typed GC) > SIGSEGV: altstack > Notifications: epoll > Architecture: amd64 > Disabled: none > > Thanks a lot in advance, > Madars >
_______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
