From: Jostein Berntsen <jbernts@broadpark.no>
To: cygwin@cygwin.com
Subject: Re: Slow ruby application: timetrap
Date: Sun, 24 Sep 2017 18:04:00 -0000 [thread overview]
Message-ID: <20170924180458.GC32439@jbsupah> (raw)
In-Reply-To: <20170922135437.GA32439@jbsupah>
On 22.09.17,15:54, Jostein Berntsen wrote:
> I have used timetrap in Cygwin for some time, but lately it has gotten
> very slow. It uses about 30 seconds just to respond, and this is a small
> program. Since this is not part of Cygwin, I install it as a gem
> install. https://github.com/samg/timetrap
>
> I use this on a work machine so it might be that some updates there
> affected it, but is there anyway I can trace why it is so slow? Other
> commands like ls, cd and similar are very fast. vim and screen hangs
> some seconds before reacting though.
>
>
Any updates on this?
Jostein
--
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
prev parent reply other threads:[~2017-09-24 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 13:54 Jostein Berntsen
2017-09-24 18:04 ` Jostein Berntsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170924180458.GC32439@jbsupah \
--to=jbernts@broadpark.no \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).