Re: Syntax for sed .. altered?
Greetings, Fergus Daly! > So far sed is the only operation where extreme sloth is exhibited. A > favoured benchtest using a long computation within Cygwin has not suddenly > slowed down, and remains consistent +/- 1 second within and between > machines. More detective work required, I guess. And any "Me Too"s very > gratefully received. Just to add to your list of exploration candidates - how is your permissions configured? Are your machine is an AD member? Is it local to the AD network, or accessing domain controller remotely? Do you run cygserver? -- With best regards, Andrey Repin Friday, July 1, 2016 14:41:34 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Syntax for sed .. altered?
>> $ find archive -type f | wc 87 871698 >> $ time find archive -type f | xargs sed -i 's/string1/string2/g' real1m2.587s user0m1.200s sys 0m12.884s >> More than a minute for 90 files is just extraordinary. >> Anybody else having a similar experience? > $ find test -type f |wc 177 1775119 > $ time find test -type f | xargs sed -i -e "s/Octave/Pippo/g" real0m5.149s user0m0.170s sys 0m1.183s BLODA ? All very perplexing. Within and between 3 different machines I get very variable timings of anything from 0m 52s to 3m 08s across 90 files, but never brief. On a 4th machine I get a more or less consistent 8s. Previously I tried reverting to an earlier cygwin1.dll (much earlier: a year) and to the [prev] offering in setup for sed. No difference in experience. On local machines I have reduced all services and cut startup processes to just antivirus (MS Security Essentials or other). No difference. So this is not a consequence of a weird file set or, apparently, a faulty Cygwin installation, but a manifestation of different machine architectures / platforms. All W7 but some 32 some 64. All protected, some differently, but having no congruence with the diverse timings above. Sio far sed is the only operation where extreme sloth is exhibited. A favoured benchtest using a long computation within Cygwin has not suddenly slowed down, and remains consistent +/- 1 second within and between machines. More detective work required, I guess. And any "Me Too"s very gratefully received. Fergus -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Syntax for sed .. altered?
On 30/06/2016 16:57, Fergus Daly wrote: find dirname -type f | xargs sed -i 's/string1/string2/g' .. just hangs. sed is unchanged from at least 2013, so it must be something else. Is is possible that this is related to a change in the Cygwin library? Thank you very much for your interest. I was premature in my assertion that sed "hangs". But it takes a crazy crazy time. I was working on a directory of 6000 text files when I reported as above. This is what happened with a directory of <90 files: ~> find archive -type f | wc 87 871698 ~> time find archive -type f | xargs sed -i 's/string1/string2/g' real1m2.587s user0m1.200s sys 0m12.884s More than a minute for 90 files is just extraordinary. Anybody else having a similar experience? (Thank you again.) Fergus Not at all $ find test -type f |wc 177 1775119 $ time find test -type f | xargs sed -i -e "s/Octave/Pippo/g" real0m5.149s user0m0.170s sys 0m1.183s BLODA ? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Syntax for sed .. altered?
>>> find dirname -type f | xargs sed -i 's/string1/string2/g' >>> .. just hangs. >> sed is unchanged from at least 2013, so it must be something else. > Is is possible that this is related to a change in the Cygwin library? Thank you very much for your interest. I was premature in my assertion that sed "hangs". But it takes a crazy crazy time. I was working on a directory of 6000 text files when I reported as above. This is what happened with a directory of <90 files: ~> find archive -type f | wc 87 871698 ~> time find archive -type f | xargs sed -i 's/string1/string2/g' real1m2.587s user0m1.200s sys 0m12.884s More than a minute for 90 files is just extraordinary. Anybody else having a similar experience? (Thank you again.) Fergus -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Syntax for sed .. altered?
On 28 June 2016 at 09:32, Marco Atzeri wrote: > On 28/06/2016 13:45, Fergus Daly wrote: >> >> For ages I have been able to run through all the files under a directory >> changing occurrences of string1 to string2 with the command >> find dirname -type f | xargs sed -i 's/string1/string2/g' >> It used to take no time at all for say 6000 files. >> Now the same command just hangs. >> The files are all text files, no binaries or anything awkward. Just don't >> understand it. >> (By contrast >> find dirname -type f | xargs md5sum >> still works just fine. 6000 files in less than a second.) >> Fergus >> > > sed is unchanged from at least 2013, so it must be something else. Is is possible that this is related to a change in the Cygwin library? Fergus, what version of Cygwin are you running? Did you recently update to 2.5.2? Did this work as expected under 2.5.1? Cheers, Chris -- Chris Sutcliffe -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Syntax for sed .. altered?
On 28/06/2016 13:45, Fergus Daly wrote: For ages I have been able to run through all the files under a directory changing occurrences of string1 to string2 with the command find dirname -type f | xargs sed -i 's/string1/string2/g' It used to take no time at all for say 6000 files. Now the same command just hangs. The files are all text files, no binaries or anything awkward. Just don't understand it. (By contrast find dirname -type f | xargs md5sum still works just fine. 6000 files in less than a second.) Fergus sed is unchanged from at least 2013, so it must be something else. Any idea on the file where is hanging ? As usual, please follow https://cygwin.com/problems.html and provide a cygcheck.out. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Syntax for sed .. altered?
For ages I have been able to run through all the files under a directory changing occurrences of string1 to string2 with the command find dirname -type f | xargs sed -i 's/string1/string2/g' It used to take no time at all for say 6000 files. Now the same command just hangs. The files are all text files, no binaries or anything awkward. Just don't understand it. (By contrast find dirname -type f | xargs md5sum still works just fine. 6000 files in less than a second.) Fergus -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
