4 ms·

GopherCon 2018 Performance Tuning Workshop

61 points by pjf 8y ago

faehnrich 8y ago
darn, was hoping this was for the protocol
- cyborgx7 8y ago
  I've stumbled uppon it recently (significant active use was before my time) and I'm in love with its simplicity compared with modern formats. I was hoping for something to get me into the protocol as well.
- shagen 8y ago
  Making gopher even faster is probably a challenge worth a talk :)
83457 8y ago
When I saw the headline I thought for a moment this was about the protocol. https://en.wikipedia.org/wiki/Gopher_(protocol) https://en.wikipedia.org/wiki/Gopher_(protocol)
- pstuart 8y ago
  Really? Would you care to talk about your work with the gopher protocol and it's application in today's computing environment?
  - simias 8y ago
    Reading the title I was actually hoping for a Gopher revival movement as a way to denounce the bloat surrounding HTTP and the mountain of protocols built haphazardly on top of it. Needless to say that I projected hard.
  - rhencke 8y ago
    There are many conventions held around technologies no longer in common use, but which still have an avid following of those that still find usefulness or enjoyment from them. For example, conferences around the Amiga and the Commodore 64 are still going on in 2018. I would honestly not be surprised if there was truly a conference dedicated to the Gopher protocol out there. If there was, I would totally want to read about it here. :)
    - mdom 8y ago
      Gopher is not the only topic, but Bitreich Con had some talks about gopher like "Migrating the web to gopher". gopher://bitreich.org/1/con/2018
      - shagen 8y ago
        Wow, there is a whole gopher community again! That's amazing!
  - tapoxi 8y ago
    I would love to see "high performance" Gopher! It would certainly be a nice way to browse websites like HN and reddit without suffering bloat (especially the reddit redesign) edit: apparently it exists! http://gopher.floodgap.com/gopher/gw?gopher://hngopher.com:70/1/live/p1/ http://gopher.floodgap.com/gopher/gw?gopher://hngopher.com:7...
    - shagen 8y ago
      Look here at web interfaces and news... there are quite a few gems: http://gopher.floodgap.com/gopher/gw?gopher://bitreich.org:70/1/lawn http://gopher.floodgap.com/gopher/gw?gopher://bitreich.org:7...
accnumnplus1 8y ago
I find the simplest way to performance tune Go programs is to wait for the next release.
- dnautics 8y ago
  I wonder are people really using go where performance is bottlenecking on code (and not say network)?
  - fmpwizard 8y ago
    About 6 years ago we adopted Scala for our server side language, and for the past 4 years we have been migrating old code that was CPU/memory hungry to go and getting very good results. All new code, if it's going to be cpu/memory intense, we write it in Go. For non C/C++ developers, Go is much easier to work with and get performance benefits that before would only be possible by porting to C, or you end up not writing idiomatic Scala, which defeats the purpose of using Scala (imho)
    - dnautics 8y ago
      That's fine, but I'm genuinely curious as to what you're finding to be cpu/memory intense. I don't know enough about scala to know if there isn't something the jvm is running poorly because "it wasn't designed to be that way". I deploy on elixir, and everything is not very big and quite acceptably performant even though I have two containerized instances of beam on an amazon t2 micro. Ooh for me, more than 50 connections a second would be unusual, but also the service really should never die.
  - artursapek 8y ago
    In most cases likely not, but there are some people using Go for CPU-bound stuff. There was a guy at gophercon yesterday who did a pretty cool demo of a raytracer he wrote in Go. He talked about the 15x performance improvement it had over using Javascript. I would definitely not choose to build a raytracer in Javascript, and probably not even in Go either. C, C++, Rust, are probably the most common choices made by people who are building something that is seriously CPU-bound.
asdkhadsj 8y ago
Anyone know of any (video) talks with a similar Go performance testing theme?
johnklos 8y ago
How is something with "gopher" in the name not about gopher? That's misleading.

61 points by pjf 8y ago

faehnrich 8y ago

darn, was hoping this was for the protocol

cyborgx7 8y ago
I've stumbled uppon it recently (significant active use was before my time) and I'm in love with its simplicity compared with modern formats. I was hoping for something to get me into the protocol as well.
shagen 8y ago
Making gopher even faster is probably a challenge worth a talk :)

83457 8y ago

When I saw the headline I thought for a moment this was about the protocol. https://en.wikipedia.org/wiki/Gopher_(protocol) https://en.wikipedia.org/wiki/Gopher_(protocol)

pstuart 8y ago
Really? Would you care to talk about your work with the gopher protocol and it's application in today's computing environment?
- simias 8y ago
  Reading the title I was actually hoping for a Gopher revival movement as a way to denounce the bloat surrounding HTTP and the mountain of protocols built haphazardly on top of it. Needless to say that I projected hard.
- rhencke 8y ago
  There are many conventions held around technologies no longer in common use, but which still have an avid following of those that still find usefulness or enjoyment from them. For example, conferences around the Amiga and the Commodore 64 are still going on in 2018. I would honestly not be surprised if there was truly a conference dedicated to the Gopher protocol out there. If there was, I would totally want to read about it here. :)
  - mdom 8y ago
    Gopher is not the only topic, but Bitreich Con had some talks about gopher like "Migrating the web to gopher". gopher://bitreich.org/1/con/2018
    - shagen 8y ago
      Wow, there is a whole gopher community again! That's amazing!
- tapoxi 8y ago
  I would love to see "high performance" Gopher! It would certainly be a nice way to browse websites like HN and reddit without suffering bloat (especially the reddit redesign) edit: apparently it exists! http://gopher.floodgap.com/gopher/gw?gopher://hngopher.com:70/1/live/p1/ http://gopher.floodgap.com/gopher/gw?gopher://hngopher.com:7...
  - shagen 8y ago
    Look here at web interfaces and news... there are quite a few gems: http://gopher.floodgap.com/gopher/gw?gopher://bitreich.org:70/1/lawn http://gopher.floodgap.com/gopher/gw?gopher://bitreich.org:7...

accnumnplus1 8y ago

I find the simplest way to performance tune Go programs is to wait for the next release.

dnautics 8y ago
I wonder are people really using go where performance is bottlenecking on code (and not say network)?
- fmpwizard 8y ago
  About 6 years ago we adopted Scala for our server side language, and for the past 4 years we have been migrating old code that was CPU/memory hungry to go and getting very good results. All new code, if it's going to be cpu/memory intense, we write it in Go. For non C/C++ developers, Go is much easier to work with and get performance benefits that before would only be possible by porting to C, or you end up not writing idiomatic Scala, which defeats the purpose of using Scala (imho)
  - dnautics 8y ago
    That's fine, but I'm genuinely curious as to what you're finding to be cpu/memory intense. I don't know enough about scala to know if there isn't something the jvm is running poorly because "it wasn't designed to be that way". I deploy on elixir, and everything is not very big and quite acceptably performant even though I have two containerized instances of beam on an amazon t2 micro. Ooh for me, more than 50 connections a second would be unusual, but also the service really should never die.
- artursapek 8y ago
  In most cases likely not, but there are some people using Go for CPU-bound stuff. There was a guy at gophercon yesterday who did a pretty cool demo of a raytracer he wrote in Go. He talked about the 15x performance improvement it had over using Javascript. I would definitely not choose to build a raytracer in Javascript, and probably not even in Go either. C, C++, Rust, are probably the most common choices made by people who are building something that is seriously CPU-bound.

asdkhadsj 8y ago

Anyone know of any (video) talks with a similar Go performance testing theme?

johnklos 8y ago

How is something with "gopher" in the name not about gopher? That's misleading.