Re: [go-nuts] How to disable all go compiler build output compressions?

[Aurora]

By empty, I mean it didn't actually contain any actual data, just zeros.
That's why it's being compressed that much.
I embedded the file into the Go code using the standard embed directive.

```
package main 
  
 import _ "embed" 
  
 //go:embed .empty 
 var data []byte
```
On Friday, 16 December 2022 at 01:15:48 UTC+3:30 kra...@skepticism.us wrote:

> Please clarify what you mean by "embedded an empty 100MB file". What 
> does "empty" mean and how did you "embed" it? Can you show us an example of 
> what you're trying to do (obviously replacing the 100MB of "empty" with a 
> placeholder).
>
> On Thu, Dec 15, 2022 at 10:58 AM Aurora  wrote:
>
>> I've embedded an empty 100MB file in my Go code, for some testing 
>> purposes.
>> When I run 'go build', the binary output would be something around 20MB.
>>
>> I want the output binary to be more than 100MB, its real size.
>>
>> How's this compression being applied to the binary?
>> How to disable all such optimisations?
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "golang-nuts" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to golang-nuts...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/golang-nuts/344ddfba-aea4-4631-b283-202a967f4b02n%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> Kurtis Rader
> Caretaker of the exceptional canines Junior and Hank
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/9101f98a-52bc-44dc-bb30-c9b81a8c194bn%40googlegroups.com.

Re: [go-nuts] How to disable all go compiler build output compressions?

[Kurtis Rader]

Please clarify what you mean by "embedded an empty 100MB file". What
does "empty" mean and how did you "embed" it? Can you show us an example of
what you're trying to do (obviously replacing the 100MB of "empty" with a
placeholder).

On Thu, Dec 15, 2022 at 10:58 AM Aurora  wrote:

> I've embedded an empty 100MB file in my Go code, for some testing purposes.
> When I run 'go build', the binary output would be something around 20MB.
>
> I want the output binary to be more than 100MB, its real size.
>
> How's this compression being applied to the binary?
> How to disable all such optimisations?
>
> --
> You received this message because you are subscribed to the Google Groups
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-nuts+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-nuts/344ddfba-aea4-4631-b283-202a967f4b02n%40googlegroups.com
> 
> .
>


-- 
Kurtis Rader
Caretaker of the exceptional canines Junior and Hank

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CABx2%3DD_o6PrEa4mDzfyGmGEBbfvaYUJ3EV3mJf1YKh01njGhhw%40mail.gmail.com.

[go-nuts] How to disable all go compiler build output compressions?

[Aurora]

I've embedded an empty 100MB file in my Go code, for some testing purposes.
When I run 'go build', the binary output would be something around 20MB.

I want the output binary to be more than 100MB, its real size.

How's this compression being applied to the binary?
How to disable all such optimisations?

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/344ddfba-aea4-4631-b283-202a967f4b02n%40googlegroups.com.

[go-nuts] Re: App Engine hasn't upgraded beyond Go 1.16, which is now out of security window

['Olivier Favre' via golang-nuts]

Hi,

I think App Engine is not getting as much development efforts as Cloud Run 
does.
I foresee it the same fate as Legacy Networks versus VPC.

That said, it looks like they were unconfortable with this situation as 
they released Go 1.18 and 1.19 (NB: not 1.17) a few days ago:
https://cloud.google.com/appengine/docs/standard/go/release-notes#December_07_2022

Cheers,
--
Olivier Favre

On Monday, September 12, 2022 at 11:33:09 AM UTC+2 Rusco wrote:

> Googles own language on Googles own cloud lags behind several version,  I 
> don't understand this :-( 
>
> Microsoft seems to be more eager to keep things up to date: 
> .NET 7 comes to Azure Functions & Visual Studio 2022 - .NET Blog 
> (microsoft.com) 
> 
>
> On Monday, 12 September 2022 at 02:33:18 UTC+1 seana...@gmail.com wrote:
>
>> I'm hoping a member of the Go team will take pity on me and prod the App 
>> Engine Go team about this. The most recent upgrade to AE's Go environment 
>> was in Nov 2021, when they started supporting Go 1.16 (see release notes 
>> below). Now that Go 1.19 is out, Go 1.16 won't be getting security fixes 
>> anymore, and App Engine Go users are in a frustrating place.
>>
>> If this is App Engine's way of telling me to move to Cloud Run 
>> (-->Dockerizing), it'd be nice if they'd just tell us that :). Otherwise, 
>> could a Googler please help us AE users out and poke AE into getting up to 
>> 1.17, 1.18, or 1.19? I don't know where to file a bug straight against AE, 
>> and I figure the Go team should be very interested in this, due to 
>> aforementioned security implications.
>>
>> https://cloud.google.com/appengine/docs/standard/go/release-notes
>>
>> Thanks,
>> Sean
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/5b659788-7c45-474d-ae5d-5ce0bd989044n%40googlegroups.com.

[go-nuts] Re: 'go run hello.go' taking ~30 seconds on windows

[Henry]

Assuming that it is a basic Hello World program, I don't have such problems 
on my Windows 11 laptop and like many Windows machines, it has antivirus, 
etc. running. I think it could be something specific to your machine or 
environment.

On Thursday, December 15, 2022 at 2:11:48 PM UTC+7 marc...@gmail.com wrote:

> It can also be something to exclude the tmp directory in which Go compiles 
> when you do a 'go run'
> (I assume you meant that when saying 'build and run')
>
> What happens if you just build?
> - Is this slow
> what happens if you just execute?
> - Is this slow?
>
> What happens if you go install some-tool and run that?
> - is that slow?
>
> Op woensdag 14 december 2022 om 21:03:26 UTC+1 schreef thepud...@gmail.com
> :
>
>> Hi Declan,
>>
>> Virus scanners can slow things down significantly on Windows, including 
>> virus scanners can go into overdrive if you are touching many files, 
>> touching files with atypical extensions, or building and then immediately 
>> executing a new binary.
>>
>> To start, you could try temporarily disabling your virus scanner and see 
>> if it helps.
>>
>> If it does help, you might be able to benefit from finer grain changes. 
>> Most virus scanners support exclusion lists if you have sufficient 
>> privileges. You could try for example excluding (1) the directories with 
>> your Go code, (2) the directory shown in 'go env GOCACHE', (3) possibly the 
>> directory shown in 'go env GOMODCACHE', and possibly others.
>>
>> I would be curious to hear your results.
>>
>> Even if this is not the particular problem you hit, it is something other 
>> gophers hit, and it would be nice to document this somewhere if it isn't 
>> already.
>>
>> Separately, I thought that Rust for example would add some default 
>> exclusions for Windows Defender, which could be an option for the Go 
>> Windows installer. However, I'm not seeing that just now based on some 
>> quick spot checking, so maybe that's something Rust only used to do, or 
>> perhaps I am thinking of something else.
>>
>> Finally, especially if you are in a corporate environment, there can be 
>> other security agents, network services, proxies, and other agents that can 
>> interfere with development performance beyond virus scanners.
>>
>> Regards,
>> thepudds
>>
>> On Wednesday, December 14, 2022 at 12:57:40 PM UTC-5 Declan Finn wrote:
>>
>>> Hi,
>>>
>>> Platform: Windows 10
>>> Go Version: 1.19.4
>>>
>>> Compile and run of the most basic helloworld program is extremely slow 
>>> on my windows machine, taking roughly 30 seconds every time.
>>> Whereas the exact same program, using the same go version, compiles and 
>>> runs in under 1 second on my Ubuntu machine.
>>> Why is it so slow on windows?
>>> I asked a collogue to do the same test on his windows machine and he 
>>> sees the same slowness.
>>> Any help would be greatly appreciated.
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/152ce89e-1318-4815-94aa-6b1edea38e4en%40googlegroups.com.