On 18/08/13 07:37, rupert THURNER wrote:
> a trace may reveal locking problems in case of multi threading
CPU usage was high, so there were no locking problems.
> , string operations causing OS calls for every character,
System CPU was negligible.
> creating and garbage collecting objects, and
On Sat, Aug 17, 2013 at 10:19:10PM +0200, rupert THURNER wrote:
(2) by when you will adjust your operating guideline, so it is clear
to faidon, ariel and others that 10 minutes tracing of an application
and getting a holistic view is mandatory _before_ restoring the
service, if it goes down for s
On Sun, Aug 18, 2013 at 5:37 AM, rupert THURNER wrote:
> On Sat, Aug 17, 2013 at 10:48 PM, bawolff wrote:
> >> yes ken, you are right, lets stick to the issues at hand:
> >> (1) by when you will finally decide to invest the 10 minutes and
> >> properly trace the gitblit application? you have the
On Sat, Aug 17, 2013 at 10:48 PM, bawolff wrote:
>> yes ken, you are right, lets stick to the issues at hand:
>> (1) by when you will finally decide to invest the 10 minutes and
>> properly trace the gitblit application? you have the commands in the
>> ticket:
>> https://bugzilla.wikimedia.org/sho
> yes ken, you are right, lets stick to the issues at hand:
> (1) by when you will finally decide to invest the 10 minutes and
> properly trace the gitblit application? you have the commands in the
> ticket:
> https://bugzilla.wikimedia.org/show_bug.cgi?id=51769
>
> (2) by when you will adjust your
On Sat, Aug 17, 2013 at 8:40 PM, Ken Snider wrote:
>
> On Aug 17, 2013, at 1:33 PM, rupert THURNER wrote:
>
>> hi faidon, i do not think you personally and WMF are particularly
>> helpful in accepting contributions. because you:
>> * do not communicate openly the problems
>> * do not report upstr
