subject:"\[PATCH 16\/15\] Add tracing to measure where most of the time is spent"

Re: [PATCH 16/15] Add tracing to measure where most of the time is spent

2016-04-20 Thread Duy Nguyen

On Wed, Apr 20, 2016 at 7:28 PM, Johannes Schindelin wrote: > Hi Duy, > > On Wed, 20 Apr 2016, Nguyễn Thái Ngọc Duy wrote: > >> All the known heavy code blocks are measured (except object database >> access). This should help identify if an optimization is effective or

Re: [PATCH 16/15] Add tracing to measure where most of the time is spent

2016-04-20 Thread Johannes Schindelin

Hi Duy, On Wed, 20 Apr 2016, Nguyễn Thái Ngọc Duy wrote: > 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).

[PATCH 16/15] Add tracing to measure where most of the time is spent

2016-04-20 Thread 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 better: - read cache line