cygwin fork()

Igor Peshansky
Fri Sep 1 14:33:00 GMT 2006

On Fri, 1 Sep 2006, clayne wrote:

> Is it just me or is cygwin fork(), or a support syscall underneath,
> terribly slow for some reason? While building projects using libtool
> (which using heavy sh, hence fork() calls) I regularly have to fire off
> 'make -j16's just to get around waiting ages when using a single make job.

While Cygwin is an *emulation* layer, and emulation is inherently slower
than straight execution, there are other potential reasons for the
slowness.  Check your anti-virus and firewall software settings.  If
possible, exclude the Cygwin filesystem from checking by those tools...
Even little things (like making the tool aware of the often-used Cygwin
programs and telling it to not check "outbound email messages" (!) sent by
those programs) can help speed up Cygwin...

A one-sentence rant: even with those changes, whenever I run a Cygwin
shell script, the stupid vsmon process takes up 100% of the CPU.  No known
solution.  Sigh...
      |\      _,,,---,,_ |
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list