As another data point, I decided to test a few implementations of http2
downloads on OSX.
Using a Go server with default frame size (16k):
Go client: 900 MB/s
Java client: 1300 MB/s
curl: 1500 MB/s
Using a Java server with default frame size (16k):
Go client: 670 MB/s
Java client: 720 MB/s
cu
Does anyone know how to configure c-for-go to work with output function
parameters - specifically slices?
I was trying to play around with adding some vulkan 1.1 and vulkan 1.2
bindings to the vulkan-go bindings (github.com/vulkan-go/vulkan), but in
order to regenerate the bindings, I needed to
Sorry, I meant to send this on the http2 thread - and I also sent prematurely :(
> On Nov 13, 2021, at 2:11 PM, robert engels wrote:
>
> As another data point, I decided to test a few implementations of http2
> downloads on OSX.
>
> Using a Go server with default frame size (16k):
>
> Go clie
As another data point, I decided to test a few implementations of http2
downloads on OSX.
Using a Go server with default frame size (16k):
Go client: 900 M/s
Java client: 1300 M/s
curl: 1500 M/s
Using a Java server with default frame size (16k):
Go client: 670 M/s
Java client: 720 M/s
curl: 80
global variables are stored in there data section of the compiled binary,
the linker imposes a 2GB size limit
the array in main can be allocated at runtime, and given enough memory, it
could succeed
On Saturday, November 13, 2021 at 5:46:29 PM UTC arthurwil...@gmail.com
wrote:
> On a 64bit Ma
On a 64bit Mac, this code:
package main
var X [^uint(0)>>14]byte
func main() {
}
produces a compile time error:
main.X: symbol too large (1125899906842623 bytes > 20 bytes)
But this compiles and crashes at runtime.
package main
func main() {
var X [^uint(0) >> 14]byte
_ = X
}
runtim
i'm trying to use http client to connect in http/2 clear text (H2C).
this works:
var dialer = &net.Dialer{
Timeout: 5 * time.Second, // fail quick
FallbackDelay: -1, // don't use Happy Eyeballs
}
rt = &http2.Transport{
AllowHTTP: true,
DialTLS: func(network, addr string, cfg *tls.Config) (net.Con
Satyendra,
>> https://github.com/ofabry/go-callvis
very interesting, but looks like a little bit out of date.
Thank you.
воскресенье, 4 июля 2021 г. в 18:57:46 UTC+3, satyendra...@gmail.com:
> Alex you can try this.
>
> https://github.com/ofabry/go-callvis
>
> Thanks and regards,
> Satyendra
On Friday, November 12, 2021 at 6:29:46 PM UTC-5 michael...@gmail.com wrote:
> FWIW (which may not be much) I've settled on explicitly naming my return
> values in the function declaration. If the function returns include an
> error, I name always name it err. The general pattern is
>
> func fo
