e a % of requests. In the past I've done that
> by enabling profiling on a set % of application servers then extrapolating
> from there.
>
>
> On Tuesday, 25 July 2017 10:55:42 UTC+10, Jaana Burcu Dogan wrote:
>>
>> It would be very speculative to provide reference num
+golang-nuts, bcc: golang-dev
On Tue, Jan 17, 2017 at 2:38 PM, Brad Fitzpatrick
wrote:
> https://groups.google.com/forum/#!forum/google-appengine-go looks like
> the right place.
>
>
> On Tue, Jan 17, 2017 at 2:30 PM, Dewey Gaedcke wrote:
>
>> Yesthat project has not been updated in 7 month
Please, find a better solution. Don't delete years of discussion and
curated content. And, the Go subreddit is the work of the community over
there and this question should be directed at them.
Minimizing the involvement and making it a unofficial space should be the
first attempt. An unofficia
Thanks for sharing the raw results.
On Thu, Nov 3, 2016 at 10:11 AM, Matt Farina wrote:
> A couple months ago we had a package management survey. Since the survey
> closed the data has been fed into the package management committee.
>
> Now we are sharing the data, that was not asked to be kept
On Thu, Oct 27, 2016 at 9:11 AM, Nate Finch wrote:
> It seems like most of the problem with this whole situation comes from the
> wording of the "warning"
>
> Please consider this a warning from the Code of Conduct working group.
>>
>
> "consider this a warning" can be interpreted as a threat (t
On Tue, Oct 18, 2016 at 12:34 PM, Jan Mercl <0xj...@gmail.com> wrote:
>
> On Tue, Oct 18, 2016 at 8:54 PM 'Jaana Burcu Dogan' via golang-nuts <
> golang-nuts@googlegroups.com> wrote:
>
> The go tool already does a lot of things, perhaps too much of them.
>
Hello gophers,
I am going to spend some time on improving the not-documented or
hard-to-use parts of the Go tools. I will mainly focus on go build and go
test. The work will consist of reorganizing manuals, proposing new
subcommands or flags to support commonly used multi-step things and so on.
T