proposal: thread-local or per-cpu storage support #22476
Comments
The problem seems to be the implementation, not the language. Please reconsider your problem and refactor the implementation by avoiding any prior form of knowledge about TLS. At that point the implementation will reveal itself as a simple, obvious, solution based on existing concepts and tools. tl;dr: don't Write C++/Java in Go, write Go in Go. |
|
@dlsniper In my case, it seems that I have no better solution with Thrift as the logical threads are created and Is there some existing solutions for my case? Thanks very much. |
|
Dup of the old #8281 |
|
As this is not a Go issue I think we should move it in one of the following mediums:
I'm sure you'll find a way to solve this. I believe this should be closed. |
|
Last question. Thanks. |
|
Because in 4.5 years of writing concurrent Go I've never needed such functionality and, for the most part, neither will the vast majority of the programmers. There are extensive, similar, threads out there proving over and over again that this is not a needed feature in order to write concurrent applications. Please use the available search solutions to find them in the above mentioned spaces. To ask the similar question: Given solutions exist outside of this particular design, why not use a different algorithm instead of requiring a change of the standard library to allow for a very specific implementation to exist? |
|
@dlsniper I write a new redis client with n(cpu num) routines and one connection per routine. The n routines will handle redis tasks together. I just send a task to the redis client and wait for the result. Thanks. By the way, your golang-plugin for ideaide seems not work on pycharm 2017.2 now. I really like this plugin! |
Please use Gogland (dedicated Go IDE) or IntelliJ IDEA Ultimate. For additional information ping me on Gophers Slack or Twitter. |
|
@dlsniper ok, thanks! |
Use case:
Write a service using Thrift framework. Thrift may have several logical threads or routines to handle request from clients.
In my implementation of the service, all the thrift logical threads will finally call my function:
function do_something()And the function
do_somethingwill read data from redis server. With thread-local support, I can create a connection to the redis server for each thread.This is very useful and I don't know how to implement it without thread-local storage support. So please consider about it. Thanks.
The text was updated successfully, but these errors were encountered: