linux套接字和多线程的C。-linuxsocketsandmultithreadinginC

1  

I don't think there would be a speed benefit with using multiple sockets unless possibly on a multihomed machine. The physical network layer cannot simultaneously send two packets at once. I would be a little concerned, though, about using a single socket without synchronization. I think it is supposed to be thread-safe, but some googling seems to indicate potential problems. I would probably put a sync around it if I were coding it because the underlying placement of the packet on the wire is going to ultimately be serialized.

我不认为使用多个套接字会带来速度上的好处，除非是在多主机上。物理网络层不能同时发送两个数据包。不过，我有点担心使用单个套接字而不进行同步。我认为它应该是线程安全的，但一些谷歌搜索似乎表明存在潜在的问题。如果我编码的话，我可能会在它周围放一个同步，因为包在电线上的底层位置最终会被序列化。

0  

Individual socket writes are synchronized for you (at the socket level), and assuming you don't have any grouping or relative ordering dependencies, this will work fine.

每个套接字写都为您同步(在套接字级别)，并且假设您没有任何分组或相对排序依赖项，这将会很好地工作。

0  

I would go for a loose-coupling approach - have all threads independent. The load doesn't seem excessive so loose-coupling appears appropriate.

我将采用松耦合的方法——让所有线程独立。负载看起来并不过分，所以松耦合看起来是合适的。

Of course, some folks will disagree but from a systems point-of-view, loose-coupling is always preferable ... where applicable :-)

当然，有些人会不同意，但是从系统的角度来看，松耦合总是更好的。适用:-)

0  

your solution work properly because you don't have same data to share between threads. But I think you can use connection pool ( make some connection and borrow to threads ) and threads in queue wait for give connection from pool.if the number of connection and thread are big performance lose[network restriction and your machine restriction] other solution that queue all thing is don't use pooling and queue all thing.but I think pooling give better performance.

您的解决方案可以正常工作，因为您没有相同的数据可以在线程之间共享。但是我认为您可以使用连接池(建立一些连接并借用到线程)和队列中的线程等待来自池的给定连接。如果连接和线程的数量很大，性能就会下降[网络限制和您的机器限制]。但我认为联营能带来更好的表现。