performance question

performance question

[Suman Kumar Ray]

 Hello,
   I have observed that if I run any program linked
with cygwin1.dll (1003.10.0.0) from windows command
prompt, it takes longer time to execute than if I run
the same under cygwin bash shell. I have tested it
with gcc -v command. I initialy thought it is because,
every time I run the program from windows cmd shell,
cygwin1.dll creates and initializes the shared region,
so it takes more time. Then I first launch bash shell
assuming its invocation will create the shared region.
Then I launch windows command shell, (i.e. so now both
bash and windows command shell exists at same time).
Still performance of "gcc -v" from windows command
shell is slower than running "gcc -v" within bash. I
am using dell laptop ,windows 2000, pentium III with
256 MB RAM.
  Can anyone tell me any reason for this slowness, and
how can I get the same performance as I get from bash
shell for any program linked with cygwin1.dll ?
 Thanks,
 Suman Ray



__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Performance question

[Brian Dessent]

w1hkj wrote:

> There is is very significant difference in cpu usage between running the
> application from the Cygwin X-terminal and running from the run command
> (with the cygwin1.dll) from Windows.
> 
> System       X-term      Windows-Run
> HP Athalon   33%           100%
> Dell 3000    3 %            55%

How much text/console output is involved in this testcase?  I find that
when run from a Windows Console, any significant amount of stdout is
much slower than when using rxvt/xterm.  I think it's partly because the
Windows Console is just a lot slower, but also because I have Lucida
Console, a Truetype font, configured for the Windows Console (as well as
Cleartype subpixel rendering enabled) which is very slow to render
compared to a fixed size bitmap font that I have configured for
rxvt/xterm.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Performance question

[Tim Prince]

w1hkj wrote:
> We are porting a real time data acquisition program for amateur radio 
> digital signal processing.  The program, fldigi, uses the Fast Light 
> Tool Kit and and a number of support libraries including PortAudio and 
> Sndfile.  The source code for this program can be found at 
> http://www.w1hkj.com.  fldigi is licensed under the GPL.
> 
> The port to Windows using Cygwin works very well.  There is just one 
> issue that needs to be addressed.  Several test platforms are used to 
> gauge performance, including an
> 
> HP notebook, 900 Mhz Athalon, 256 Mg RAM, and
> Dell Dimension 3000, dual processor 3.0 GHz, 1 G RAM.
> 
> There is is very significant difference in cpu usage between running the 
> application from the Cygwin X-terminal and running from the run command 
> (with the cygwin1.dll) from Windows.
> 
> System       X-term      Windows-Run
> HP Athalon   33%           100%
> Dell 3000    3 %            55%
> 
> 
> We would appreciate any assistance or suggestions on how to improve the 
> performance when linking to cygwin1.dll.
> 
If you are running single thread, with HT enabled, a 50% performance meter 
indication on the Dell is entirely normal.  Xterm performance questions 
would be appropriate to that mailing list.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Performance question

[w1hkj]

We are porting a real time data acquisition program for amateur radio 
digital signal processing.  The program, fldigi, uses the Fast Light 
Tool Kit and and a number of support libraries including PortAudio and 
Sndfile.  The source code for this program can be found at 
http://www.w1hkj.com.  fldigi is licensed under the GPL.

The port to Windows using Cygwin works very well.  There is just one 
issue that needs to be addressed.  Several test platforms are used to 
gauge performance, including an

HP notebook, 900 Mhz Athalon, 256 Mg RAM, and
Dell Dimension 3000, dual processor 3.0 GHz, 1 G RAM.

There is is very significant difference in cpu usage between running the 
application from the Cygwin X-terminal and running from the run command 
(with the cygwin1.dll) from Windows.

System       X-term      Windows-Run
HP Athalon   33%           100%
Dell 3000    3 %            55%


We would appreciate any assistance or suggestions on how to improve the 
performance when linking to cygwin1.dll.

Thank you.

David Freese
for fldigi development team.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/