Interface Dispatch (2018)

Re:Interface Dispatch (2018) by Insanity on Thursday April 18, 2019 @07:02AM (#19690103)

Speaking of interfaces in Go, can anyone explain this particular result? We've done a benchmark recently at work to test which way we would best represent a set. (Linux, go1.12)

      map[string]bool
      map[string]struct{}
      map[string]interface{} // where we put an empty struct in it.

results:

     BenchmarkBoolSet-4              5886572           223 ns/op          39 B/op           0 allocs/op
     BenchmarkStructSet-4            6716685           206 ns/op          32 B/op           0 allocs/op
     BenchmarkInterfaceSet-4         4299072           313 ns/op         115 B/op           0 allocs/op

(I'm aware this is a bit of a tangent to TFA)

[ Parent | on HN ]

Re:Interface Dispatch (2018) by bouk on Thursday April 18, 2019 @07:25AM (#19690186)

Can’t really say what’s going on here without seeing some code.

[ Parent | on HN ]

Re:Interface Dispatch (2018) by Insanity on Thursday April 18, 2019 @09:05AM (#19690666)

Well the code is the same for all of them (but when using a bool map we assign true instead of empty struct). So we run this code inside a benchmarking function:

      m := map[int]interface{}
      // or m := map[int]struct{}
      for i := 0; i < t.N; i++ {
           m[i] = struct{}{}
      }

edit: fix code.

[ Parent | on HN ]

Re:Interface Dispatch (2018) by wyufro on Thursday April 18, 2019 @09:56AM (#19691018)

I'm speculating, but sizeof(bool) == 1, sizeof(struct{}) == 0 and sizeof(interface{}) == 8, so might be as simple as that.

https://play.golang.org/p/5acy87JLD3i

[ Parent | on HN ]

Re:Interface Dispatch (2018) by Insanity on Thursday April 18, 2019 @10:42AM (#19691354)

Yup that well could be it!

[ Parent | on HN ]