Re: [go-nuts] Go Performance

Final update on this, using a technique from my HFT days, by spinning the main routing thread longer before parking I reduced the latency numbers with Java to: duration avg 186828 min 152425 max 968440 which are back inline with the original that did not use the intermediary queue. It did not m

Re: [go-nuts] Go Performance

Just an update for those who may be interested. With some improvements to the Java side, and using a more realistic test of 1 pub and 1 sub, the results: Java: without SSL, 3450k msgs per sec with SSL, 1300k msgs per sec Go: without SSL, 3600k msgs per sec with SSL, 1800k msgs per sec Clearly

Re: [go-nuts] Go Performance

Btw, the math was off here, with 3 million vs. 5 million ops a second (and these are essentially IO ops - sending messages to the broker), the difference is 0.13 microsecs per op - or 130 nanos. Pretty insignificant for IO based tasks. > On Oct 30, 2018, at 8:10 AM, Robert Engels wrote: > > I

Re: [go-nuts] Go Performance

I’ve written lots of network service code. I understand what’s available. Actually, for a small number of clients threads are faster than async/nio. In this case there is only a single active thread during the test. The main benefit of using nio is that you can avoid the java space to native c

[go-nuts] Go Performance

Some notes on your java impl: You really want to use a framework for handling the connections and threading, its tricky in java. Your current implementation creates 2 new threads on each connection which is wasteful and very expensive. For threading please see: https://stackoverflow.com/questio

Re: [go-nuts] Go Performance

On Mon, Oct 29, 2018 at 1:53 PM, robert engels wrote: > Hello Gophers, > > I’ve been chastised in the past regarding some of my Go performance tests - > using Java as a baseline. In most of these micro-benchmarks Go has performed > more poorly than expected. > > So, I ported nats (https://nats.io)

Re: [go-nuts] Go Performance

On Mon, Oct 29, 2018 at 9:53 PM robert engels wrote: > In most of these micro-benchmarks Go has performed more poorly than expected. Micro-benchmarks? You can stop right here. -- -j -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubsc

[go-nuts] Go Performance

Hello Gophers, I’ve been chastised in the past regarding some of my Go performance tests - using Java as a baseline. In most of these micro-benchmarks Go has performed more poorly than expected. So, I ported nats (https://nats.io ) message broker (which is written in Go) to J

Re: [go-nuts] Go performance in regexdna

On Thursday, September 1, 2016 at 2:45:42 PM UTC-7, Ian Lance Taylor wrote: > > On Thu, Sep 1, 2016 at 1:34 PM, DrGo > > wrote: > > What is the reason for Go particularly poor performance in regexdna as > shown here? > > > https://benchmarksgame.alioth.debian.org/u64q/performance.php?test=re

Re: [go-nuts] Go performance in regexdna

Thanks Ian, Very helpful -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.

Re: [go-nuts] Go performance in regexdna

On Thu, Sep 1, 2016 at 1:34 PM, DrGo wrote: > What is the reason for Go particularly poor performance in regexdna as shown > here? > https://benchmarksgame.alioth.debian.org/u64q/performance.php?test=regexdna In several past discussions of this topic the consensus has been that most languages ar

[go-nuts] Go performance in regexdna

What is the reason for Go particularly poor performance in regexdna as shown here? https://benchmarksgame.alioth.debian.org/u64q/performance.php?test=regexdna Cheers -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group