Re: Attempt at a real world benchmark

I'd imagine that "opt-in" could even mean you have to install a separate program/package to send data that's been collected. If it were very separate from the compiler itself, would these security concerns still be a problem? I for one would go through the effort of opting in since I want the

Re: Attempt at a real world benchmark

I would opt-in. I also agree with Simon that privacy is no longer a big deal although I do believe that most companies do telemetry with an opt in policy. If it's opt-in why would anyone have a problem with telemetry? On Fri, Dec 9, 2016 at 1:46 PM Tom Murphy wrote: > On Fri,

Re: Attempt at a real world benchmark

> It could tell us which language features are most used. A lot could be gleaned just by analyzing the packages on Hackage though. For example: https://www.reddit.com/r/haskell/comments/31t2y9/distribution_of_ghc_extensions_on_hackage/ ___ ghc-devs

Re: Attempt at a real world benchmark

On Fri, Dec 9, 2016 at 9:50 AM, Simon Peyton Jones via ghc-devs < ghc-devs@haskell.org> wrote: > The big issue is (a) design and implementation effort, and (b) dealing > with the privacy issues. And (c) not everyone is going to upgrade their ghc, even if you backport the telemetry to older

Re: Attempt at a real world benchmark

On Fri, Dec 9, 2016 at 4:50 AM, Simon Peyton Jones via ghc-devs < ghc-devs@haskell.org> wrote: > I have wanted telemetry for years. ("Telemetry" is the term Microsoft, > and I think others, use for the phone-home feature.) > > It would tell us how many people are using GHC; currently I have

Re: Attempt at a real world benchmark

Hi, Am Freitag, den 09.12.2016, 13:54 +0800 schrieb Moritz Angermann: > > I am not sure what you are saying. Are you proposing the maintain a > > benchmark set outside GHC, or did you get the impression that I am > > proposing it? > > Yes, that’s what *I* am proposing for the reasons I

Re: Attempt at a real world benchmark

Sorry for hijacking the thread, but On 12/ 9/16 10:50 AM, Simon Peyton Jones via ghc-devs wrote: I have wanted telemetry for years. ("Telemetry" is the term Microsoft, and I think others, use for the phone-home feature.) telemetry or better "call-home", this is very dangerous idea to even

RE: Attempt at a real world benchmark

Arantsson | Sent: 09 December 2016 07:32 | To: ghc-devs@haskell.org | Subject: Re: Attempt at a real world benchmark | | On 2016-12-08 17:04, Joachim Breitner wrote: | > Hi, | > | > Am Donnerstag, den 08.12.2016, 01:03 -0500 schrieb Joachim Breitner: | >> I am not sure

Re: Attempt at a real world benchmark

>> Actually, now that I think about it: What about if this were integrated >> into the Cabal infrastructure? If I specify "upload-perf-numbers: True" >> in my .cabal file, any project on (e.g.) GitHub that wanted to opt-in >> could do so, they could build using Travis, and voila! >> > >

Re: Attempt at a real world benchmark

On 2016-12-09 08:31, Bardur Arantsson wrote: > Actually, now that I think about it: What about if this were integrated > into the Cabal infrastructure? If I specify "upload-perf-numbers: True" > in my .cabal file, any project on (e.g.) GitHub that wanted to opt-in > could do so, they could build

Re: Attempt at a real world benchmark

On 2016-12-08 17:04, Joachim Breitner wrote: > Hi, > > Am Donnerstag, den 08.12.2016, 01:03 -0500 schrieb Joachim Breitner: >> I am not sure how useful this is going to be: >> + Tests lots of common and important real-world libraries. >> − Takes a lot of time to compile, includes CPP macros and

Re: Attempt at a real world benchmark

> On Dec 9, 2016, at 1:00 PM, Joachim Breitner wrote: > > Hi, > > Am Freitag, den 09.12.2016, 09:50 +0800 schrieb Moritz Angermann: >> Hi, >> >> let me thank you perusing this! >> I am not sure how useful this is going to be: + Tests lots of common and

Re: Attempt at a real world benchmark

Hi, let me thank you perusing this! >> I am not sure how useful this is going to be: >> + Tests lots of common and important real-world libraries. >> − Takes a lot of time to compile, includes CPP macros and C code. >> (More details in the README linked above). > > another problem with the

Re: Attempt at a real world benchmark

Hi, Am Donnerstag, den 08.12.2016, 01:03 -0500 schrieb Joachim Breitner: > I am not sure how useful this is going to be: >  + Tests lots of common and important real-world libraries. >  − Takes a lot of time to compile, includes CPP macros and C code. > (More details in the README linked above).

RE: Attempt at a real world benchmark

I'm delighted to see all this traffic about GHC perf -- thank you. 277 modules sounds like quite a lot; but in general a test suite that took a while (minutes, not hours) to compile would be fine. We can run it on a nightly server somewhere. Having a dashboard where you can see the results