Why do you say it will be single threaded? I ask as even with a single core multiple threads can be beneficial.
Even with GOMAXPROCS=1 the go runtime will multiplex multiple requests efficiently without you thinking about it. On Fri, 26 May 2017 at 19:32, <streckertda...@gmail.com> wrote: > This might be a silly question, but I’m going to ask anyway. I'm working > on a High-Frequency Trading program for educational purposes. I don’t > expect it to make money; it’s a fun project to learn about socket > programming. > > > It will be a single-threaded program running on one CPU that will “talk” > to two different API endpoints at a currency brokerage firm called Oanda. > Because the program will be single threaded, I don’t need to really take > advantage of Go’s concurrency support. > > > For a single-threaded/single CPU program, is there any reason to consider > Go instead of C when speed is the most important consideration? Is there > anything you’d recommend I think about? Any information is appreciated. > > -- > 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.com/d/optout. > -- 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.com/d/optout.
