Re: [PATCH v8 18/19] Add tracing to measure where most of the time is spent

On Fri, May 6, 2016 at 5:48 AM, Junio C Hamano wrote: > David Turner writes: > >> From: Nguyễn Thái Ngọc Duy >> Subject: Re: [PATCH v8 18/19] Add tracing to measure where most of the time >> is spent > > trace: measure where the time is spent in the index-heavy

Re: [PATCH v8 18/19] Add tracing to measure where most of the time is spent

David Turner writes: > From: Nguyễn Thái Ngọc Duy > Subject: Re: [PATCH v8 18/19] Add tracing to measure where most of the time > is spent trace: measure where the time is spent in the index-heavy operations -- To unsubscribe from this list: send the line "unsubscribe git&quo

[PATCH v8 18/19] Add tracing to measure where most of the time is spent

From: Nguyễn Thái Ngọc Duy All the known heavy code blocks are measured (except object database access). This should help identify if an optimization is effective or not. An unoptimized git-status would give something like below (92% of time is accounted). To sum up the effort of making git scale