> turns out that Comodo Firewall (Free version) loads a DLL in each process
> that is the cause of the delay.
> Although I only use the Firewall, and do not use any "AntiVirus" features,
> still it causes delay during startup of a process.
>
> However, after disabling it -- which did speed up pr
> If you use http://www.dependencywalker.com/ on bash.exe with view/full
> paths enabled, does the Comodo Firewall dll stand out or is it just
> another .dll loaded from windows\system32?
>
> Regards,
> Lee
I use Process Explorer to view in-process .dlls:
C:\WINDOWS\system32\guard32.dll
Regards
On 24/09/2015 19:46, Lee wrote:
On 9/24/15, litter wrote:
On 24/09/2015 11:57, litter wrote:
Obviously something is. The FAQ entry does not mention performance, but
real failures.
How to further diagnose this?
I took the plunge and spent almost a full day trying to find the cause.
... s
On 9/24/15, litter wrote:
>> On 24/09/2015 11:57, litter wrote:
>>> Obviously something is. The FAQ entry does not mention performance, but
>>> real failures.
>>> How to further diagnose this?
>
> I took the plunge and spent almost a full day trying to find the cause.
... snip ...
> turns out t
On 24/09/2015 18:24, lit...@null.net wrote:
>> On 24/09/2015 11:57, lit...@null.net wrote:
>>> Obviously something is. The FAQ entry does not mention performance, but
>>> real failures.
>>> How to further diagnose this?
>
> I took the plunge and spent almost a full day trying to find the cause.
>
> Maybe:
>
> strace bash -c 'time cat some-file | while read i;do echo
> $i;/bin/true;done'
>
> Haven't tested it.
>
> Simplify the command:
>
> for((i=0;i<150;i++));do /bin/true;done
>
> to rule out a pipe-problem.
Thanks for the tips! Used a variant on the for loop to simplify the problem.
> On 24/09/2015 11:57, lit...@null.net wrote:
>> Obviously something is. The FAQ entry does not mention performance, but real
>> failures.
>> How to further diagnose this?
I took the plunge and spent almost a full day trying to find the cause.
1. Booting into Safe Mode gave a huge performance bo
On 24/09/2015 11:57, lit...@null.net wrote:
Obviously something is. The FAQ entry does not mention performance, but real
failures.
How to further diagnose this?
together with the cygcheck output that I already mentioned
I suggest
1) to look on
/proc/self/maps or /proc//maps
to looks for s
> On 23/09/2015 17:17, lit...@null.net wrote:
for a file of 167 lines. Process Explorer showed a CPU load of 20% on
bash.exe, which was almost completely Kernel time.
Is such high Kernel load normal?
>>>
>>> may be. forks are time consuming and your command is spending all the
>>> t
---
> I'm not running any antivirus as far as I'm aware of (I do run a Comodo
> firewall with all "virus" scanning disabled).
> I checked again, and it really is the Bash.exe which is consuming a lot of
> Kernel time. I didn't spot another process k
On 23/09/2015 17:17, lit...@null.net wrote:
for a file of 167 lines. Process Explorer showed a CPU load of 20% on bash.exe,
which was almost completely Kernel time.
Is such high Kernel load normal?
may be. forks are time consuming and your command is spending all the
time in fork
So why is i
> lit...@null.net:
> Wed, 23 Sep 2015 10:52:26 +0200
> ---
>> Hi all,
>>
>> I noticed that doing simple loops in Bash takes unexpectedly long under
>> Cygwin on a Windows XP 32 bit machine
>> (CYGWIN_NT-5.1 2.2.1(0.289/5/3) 2015-08-20 11:40 i686 C
>> for a file of 167 lines. Process Explorer showed a CPU load of 20% on
>> bash.exe, which was almost completely Kernel time.
>> Is such high Kernel load normal?
>
> may be. forks are time consuming and your command is spending all the
> time in fork
So why is it spending all its time in fork?
On 23/09/2015 10:52, lit...@null.net wrote:
Hi all,
I noticed that doing simple loops in Bash takes unexpectedly long under Cygwin
on a Windows XP 32 bit machine
(CYGWIN_NT-5.1 2.2.1(0.289/5/3) 2015-08-20 11:40 i686 Cygwin)
I already followed the FAQ advice in trying to determine general caus
lit...@null.net:
Wed, 23 Sep 2015 10:52:26 +0200
---
> Hi all,
>
> I noticed that doing simple loops in Bash takes unexpectedly long under
> Cygwin on a Windows XP 32 bit machine
> (CYGWIN_NT-5.1 2.2.1(0.289/5/3) 2015-08-20 11:40 i686 Cygwin)
>
>
Hi all,
I noticed that doing simple loops in Bash takes unexpectedly long under Cygwin
on a Windows XP 32 bit machine
(CYGWIN_NT-5.1 2.2.1(0.289/5/3) 2015-08-20 11:40 i686 Cygwin)
I already followed the FAQ advice in trying to determine general causes, and
made a 'shadow' copy of /etc/passwd
16 matches
Mail list logo
