Christopher Layne wrote:
$ uname -a; uptime; time echo 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74
75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 |
xargs -n1 >/dev/null
CYGWIN_NT-5.2 opteron 1.7.0s(0.165/4/2) 20070215 07:41:32 i686 Cygwin
10:05:57 up 1 day, 11:10, 0 users, load average: 0.00, 0.00, 0.00
real 0m5.185s
user 0m0.150s
sys 0m0.573s
[OT]
On an Opteron?! I get 1.1 seconds on a low-end Core 2 Duo with WinXP.
Something else also the matter at your end. (Of course, my Linux box,
on an older Core Duo, also does this in 0.085 seconds, so your Linux box
is slow, too :-) ).
But process creation is well-known to be slow in Cygwin, for completely
unavoidable reasons (having to emulate a nearly full layer of POSIX
semantics *on top of* Windows processes, which are already slow(er) to
start with).
--
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/
