[go-nuts] Re: strip / reduce module compile size

2024-06-15 Thread Peter Galbavy
If end binary size is a constraint, try "upx" to compress the end binary. I regularly get 3x compression - but lose all debug options, obviously. Works on most OSes for executables. On Friday 14 June 2024 at 22:43:53 UTC+1 Tony M wrote: > Thank you to github.com/jondot/goweight I was able to de

Re: [go-nuts] Re: strip / reduce module compile size

2024-06-15 Thread Tobias Klausmann
Hi! On Sat, 15 Jun 2024, Peter Galbavy wrote: > If end binary size is a constraint, try "upx" to compress the end binary. I > regularly get 3x compression - but lose all debug options, obviously. Works > on most OSes for executables. Be aware that there are further consequences to using upx, b

[go-nuts] coroutine size

2024-06-15 Thread cheng dong
thanks to runtime.newcoro/coroswitch and now we could do more things with coroutine. but it seems every newcoro create a full g which is 448B in size. maybe it is too heavy for a coroutine both in size and in schedule granularity ? -- You received this message because you are subscribed to the

[go-nuts] Re: coroutine size

2024-06-15 Thread cheng dong
maybe coroutine could be implented inside a g in future hopefully On Saturday, June 15, 2024 at 10:23:01 PM UTC+8 cheng dong wrote: > thanks to runtime.newcoro/coroswitch and now we could do more things with > coroutine. but it seems every newcoro create a full g which is 448B in > size. maybe

[go-nuts] Re: coroutine size

2024-06-15 Thread cheng dong
sorry, i found that 500k stack size might be nesessary for a coroutine, so its not a problem. On Saturday, June 15, 2024 at 10:24:18 PM UTC+8 cheng dong wrote: > maybe coroutine could be implented inside a g in future hopefully > > On Saturday, June 15, 2024 at 10:23:01 PM UTC+8 cheng dong wrote

[go-nuts] Re: coroutine size

2024-06-15 Thread cheng dong
ahh, i really want to say is, can golang offer user a stateless coroutine. On Saturday, June 15, 2024 at 11:16:02 PM UTC+8 cheng dong wrote: > sorry, i found that 500k stack size might be nesessary for a coroutine, so > its not a problem. > > On Saturday, June 15, 2024 at 10:24:18 PM UTC+8 cheng

Re: [go-nuts] Re: coroutine size

2024-06-15 Thread Robert Engels
I don’t think that is possible. You can have stackless coroutines, but if a coroutine has no state at all it would simply be implements as a method call chain without parameters in an executor. I doubt these are very useful. On Jun 15, 2024, at 10:08 PM, cheng dong wrote:ahh, i really want to say