Migrated WordGap from Python to Go 1

Re:Migrated WordGap from Python to Go 1 by NateDad on Saturday March 23, 2013 @04:14PM (#5429593)

And the app engine only supports a single thread for Go, imagine if you could make it multi-threaded.

[ Parent | on HN ]

Re:Migrated WordGap from Python to Go 1 by phasevar on Saturday March 23, 2013 @04:20PM (#5429618)

Multi-threaded wouldn't help the case of a single request, which is what this post is reporting latency numbers on.

[ Parent | on HN ]

Re:Migrated WordGap from Python to Go 1 by voidlogic on Saturday March 23, 2013 @04:29PM (#5429645)

True, but it would help average request latency under load. I am hoping with Go 1.1 RC coming out next month that Google might enable multi-threading on the GAE.

Note: Even with Go only given a single core a developer can still write a Go program so they are concurrent. That way when one goroutine blocks on IO, another can use the CPU to make progress; furthermore, when multi-threading is enabled the performance upgrade will be substantial and seamless.

[ Parent | on HN ]

Re:Migrated WordGap from Python to Go 1 by Encosia on Saturday March 23, 2013 @05:45PM (#5429901)

Assuming he's searching a trie to build the list of anagrams, he could distribute a single request's work over a thread per letter.

[ Parent | on HN ]

Re:Migrated WordGap from Python to Go 1 by Evbn on Sunday March 24, 2013 @02:23AM (#5431331)

If he has multi core, which is often missing in a VM.

[ Parent | on HN ]