http://www.worldcrunch.com/poisoning-well-nestl-accused-expl...
376 karma · joined March 7, 2013
GitHub: https://github.com/julienschmidt
We're hiring! https://grnh.se/a27fea202us
http://www.worldcrunch.com/poisoning-well-nestl-accused-expl...
The up-to-date Go Users page is at http://code.google.com/p/go-wiki/wiki/GoUsers
I find it hard to believe them, though. They seem to be against anything as soon as it gets unpopular.
And yes, the US army bases in Germany are left overs from the allied occupation after WW II
I think the green party (Bündnis 90 / Die Grüne) will profit considerably more from this. They are know promoters of privacy and personal rights. "Die Linke" could also profit from this.
Time for a "Arrested Development" scene! http://www.dailymotion.com/video/xohzz1_lindseys-cage-dance_...
98,4% in a speed test which highly relies on the destination server and the routing is a perfect result.
1. Use absolute paths for the Go tools: $ /home/paul/go-tip/bin/go run myfile.go
2. Set the GOPATH every time accordingly (script)
3. Rename the folder. For example on my Windows PC I have GOPATH pointed to D:/dev/go. In the dev folder I have Go installations in go/ (currently 1.1), go1.0.3 (guess the version) and go-tip. If I want to use another version I just rename the folder to go/
Go 1.1 comes with some impressive performance optimizations, but there are more optimizations that can be done and there are already some great ideas discussed, like a Preemptive Scheduler.
Just see what performance related changes where already made since the Go 1.1 release last week:
• SSE-powered string/bytes compare: http://code.google.com/p/go/source/detail?r=b2f1f8cb2fcb7025...
• less allocations in the JSON package: http://code.google.com/p/go/source/detail?r=00d69aa6619e77d8...
• optimizations to malloc(): http://code.google.com/p/go/source/detail?r=0fe374e887455a57... and http://code.google.com/p/go/source/detail?r=931a7362e30c2139...
• optimized aeshash: http://code.google.com/p/go/source/detail?r=80c8a9f81e4816e0...
• faster x86 memmove: http://code.google.com/p/go/source/detail?r=4cb93e2900d0c748...
• less allocations in the buffered I/O package: http://code.google.com/p/go/source/detail?r=bce231eb0fdd4bbe...
• optimizations in the flate compression package: http://code.google.com/p/go/source/detail?r=bd653e485f1d9b5c...
• optimizations to the net/http package: http://code.google.com/p/go/source/detail?r=647f336edfe88a31... and http://code.google.com/p/go/source/detail?r=d1d76fc0ab6a33f1...
• integrated network poller for BSD: http://code.google.com/p/go/source/detail?r=9d60132d77847262...
I apologize if you feel we stepped on your opinions in any fashion.
I don't ;)I'm just not so happy about making the queries this way: http://i.imgur.com/u9Nx5.png
Of course I will try to help solving this issue, but it is hard to contribute without testing, since I have no idle server or suitable spare computer around where I could run this tests properly. But my PC seems to have a somewhat similar configuration to your "dedicated i7 hardware". I hope I manage to set up the test environment in a dual-boot soon.
Like in round 4 (since the related code hasn't changed) the many concurrent spawned goroutines probably get in each others way, causing a high latency and low throughput.
There was a reversion of the test without goroutines, which I think performed better. But I was told the goroutines version is more realistic... (I don't share this opinion).
To be fair, this version had also a manual connection pool to address a previous bug.
Also Go's database connectivity is not very mature yet. There is still a lot of work to do. I'm pretty sure it can and will be done.
Edit: yeah right Mono and w/e
Edit: dylanvee was faster, the NX-bit is the underlying hardware feature
other issues: probably not, since these are new issues that are being worked on
That's not the drivers fault: https://code.google.com/p/go/issues/detail?id=4804
Please keep in mind, that the database/sql package is - like Go itself - still very young. There is still a lot of work to do compared to mature libraries like JDBC, but it will improve with every release.