Posted Jun 3, 2010 0:07 UTC (Thu) by mhelsley (subscriber, #11324)
Parent article: Giggle: A Git GUI
"The performance of Giggle is rather poor, especially considering that the underlying tool has a definite focus on speed.
...
[giggle] can sometimes take up to ten seconds.
...
When scrolling through history, Giggle will just pause and eat CPU for a while."
I've had the same experiences with the commandline interface alone. Sometimes without consuming much in the way of cpu, disk, or network resources it will still pause for 5-10 seconds.
Posted Jun 3, 2010 15:17 UTC (Thu) by iabervon (subscriber, #722)
[Link]
You might try strace on that; at one point someone reported a similar issue, which turned out to be some configuration problem with name resolution. From their reported strace, their system seemed to be trying to get responses from a time server that wasn't responding (fittingly named "timesink.svana.net"); it would wait 5 seconds twice before carrying on with a local timestamp or something like that.