We used go1.16.5 before go1.19 released. Occassionally we found ballast
takes up RSS :)
About go1.19 GOMEMLIMIT, I tested and have some thinking:
- GOMEMLIMIT is a soft limit, if we deploy by per container per service,
GOGC=off+GOMEMLIMIT=70%*totalMemory, it may works as expected. And it may
re
Indeed, the rules for quoting and parsing command lines are considerably
different even in different context on the same OS (Windows) and so
successfully building a command line to be run requires detailed knowledge
of the context in which it will be evaluated.
Unix systems are at least relativ
Oddly the benchmark times are back to normal. (after a few reboots and
selinux fiddling (turning it off and then back on).
Probably some local soaking was needed for the new system. Sorry for the
noise (and thanks for the strace tip)
On Tuesday, November 15, 2022 at 6:34:45 PM UTC-5 Ian Lance T
On Tue, Nov 15, 2022 at 3:26 PM Anthony Starks wrote:
>
> I just updated my X1 Carbon 5th gen, (8Gb RAM, 256 Gb SSD) system from Fedora
> Linux 36 to 37 and the same Go binaries (pdfdeck [1]) are about 2x slower.
> The code was built with Go 1.19.3 and has been stable. Rebuilding with a
> fre
I just updated my X1 Carbon 5th gen, (8Gb RAM, 256 Gb SSD) system from
Fedora Linux 36 to 37 and the same Go binaries (pdfdeck [1]) are about 2x
slower. The code was built with Go 1.19.3 and has been stable. Rebuilding
with a fresh install of go has no impact.
Question: is there anything i
On Sat, Nov 12, 2022 at 12:40 AM Mike Schinkel wrote:
> Hi G.,
>
> It takes guts to make a proposal in the Go community. Kudos for doing so.
>
Or recklessness :-). Thanks.
>
> However, the issue with this proposal for me is the issue I have with
> almost(?) every other proposal to handle erro
