Re: Feedback request regarding speed optimisations in trace mode

2019-06-22 Thread Mihir Luthra
Hi, > > With modern macOS and modern hardware there are performance effects that > you can't control, perhaps most significantly thermal throttling, but > also background jobs like Time Machine backups and iCloud sync. > > You need to apply a little bit of statistical theory. Standard error >

Re: Feedback request regarding speed optimisations in trace mode

2019-06-14 Thread Joshua Root
On 2019-6-13 16:40 , Mihir Luthra wrote: > Hi, >   > > I would like to see the time for each run (if 10 runs, then 10 columns > i.e., xx_run1, xx_run2, ...), rather than only average of them. > > Collect as much as insights we could, maybe we find some pattern or > something that

Re: Feedback request regarding speed optimisations in trace mode

2019-06-14 Thread Mihir Luthra
Hi, > > Not necessary to stick to 10 runs, just because I said so. It can be > even 3 or 5 runs. Whichever you feel seem to be good enough to give > some insights. E.g., you might feel that after 3 runs you are getting > constant time and not much difference, in another case you might get > all

Re: Feedback request regarding speed optimisations in trace mode

2019-06-13 Thread Jackson Isaac
Hi Mihir, On Thu, Jun 13, 2019 at 8:40 AM Mihir Luthra <1999mihir.lut...@gmail.com> wrote: > > Hi, > >> >> I would like to see the time for each run (if 10 runs, then 10 columns >> i.e., xx_run1, xx_run2, ...), rather than only average of them. >> >> Collect as much as insights we could, maybe we

Re: Feedback request regarding speed optimisations in trace mode

2019-06-13 Thread Mihir Luthra
Hi, > I would like to see the time for each run (if 10 runs, then 10 columns > i.e., xx_run1, xx_run2, ...), rather than only average of them. > > Collect as much as insights we could, maybe we find some pattern or > something that might help us (not sure what though). Since I have a > feeling,

Re: Feedback request regarding speed optimisations in trace mode

2019-06-12 Thread Jackson Isaac
On Sun, Jun 9, 2019 at 6:01 PM Mihir Luthra <1999mihir.lut...@gmail.com> wrote: > > Hi jan, > >> >> How exactly were these numbers obtained? Is it one run? >> An average of ten runs? All following a complete distclean? >> Is it the "real" time as reported by time(1) or somethin else? >> What are

Fwd: Feedback request regarding speed optimisations in trace mode

2019-06-09 Thread Mihir Luthra
Hi, > This is certainly an improvement. How does it compare with running the > same builds without trace mode? The ideal scenario would of course be to > have trace mode incur only a barely noticeable performance penalty. > Kindly check out this link. I made the comparisons again for those

Re: Feedback request regarding speed optimisations in trace mode

2019-06-09 Thread Mihir Luthra
Hi jan, > How exactly were these numbers obtained? Is it one run? > An average of ten runs? All following a complete distclean? > Is it the "real" time as reported by time(1) or somethin else? > What are the other times reported by time(1), as in > > $ time sleep 5 > 0m05.01s real

Re: Feedback request regarding speed optimisations in trace mode

2019-06-08 Thread Joshua Root
On 2019-6-7 06:38 , Mihir Luthra wrote: > Hi everyone, > > I have been working on trace mode optimisation project. > I have added the functionalities to improve the speed. [1] > I tested it on some ports, and it works stably. > > Here are some comparisons I made on my machine: > > In Original

Feedback request regarding speed optimisations in trace mode

2019-06-06 Thread Mihir Luthra
Hi everyone, I have been working on trace mode optimisation project. I have added the functionalities to improve the speed. [1] I tested it on some ports, and it works stably. Here are some comparisons I made on my machine: In Original Code Port gettext (+ deps :ncurses, libiconv, gperf) : 13