StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2281756
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-02-17T15:08:59.740
FavoriteCount
0
LastActivityDate
2018-02-14T14:10:12.467
LastEditDate
2018-02-14T14:10:12.467
LastEditorUserId
359181
OwnerUserId
203667
ParentId
2281204
PostTypeId
2
Score
55
ViewCount
0
LastEditorDisplayName
text
Body
When selecting your IPC you should consider causes for performance differences including transfer buffer sizes, data transfer mechanisms, memory allocation schemes, locking mechanism implementations, and even code complexity. Of the available IPC mechanisms, the choice for performance often comes down to <a href="http://en.wikipedia.org/wiki/Unix_socket" rel="nofollow noreferrer">Unix domain sockets</a> or <a href="http://en.wikipedia.org/wiki/Named_pipe" rel="nofollow noreferrer">named pipes (FIFOs)</a>. I read a paper on <a href="http://osnet.cs.binghamton.edu/publications/TR-20070820.pdf" rel="nofollow noreferrer">Performance Analysis of Various Mechanisms for Inter-process Communication</a> that indicates Unix domain sockets for IPC may provide the best performance. I have seen conflicting results <a href="http://cybertiggyr.com/throughput/throughput.html" rel="nofollow noreferrer">elsewhere</a> which indicate pipes may be better. When sending small amounts of data, I prefer named pipes (FIFOs) for their simplicity. This requires a pair of named pipes for bi-directional communication. Unix domain sockets take a bit more overhead to setup (socket creation, initialization and connection), but are more flexible and may offer better performance (higher throughput). You may need to run some benchmarks for your specific application/environment to determine what will work best for you. From the description provided, it sounds like Unix domain sockets may be the best fit. <hr> <a href="https://beej.us/guide/bgipc/" rel="nofollow noreferrer">Beej's Guide to Unix IPC</a> is good for getting started with Linux/Unix IPC.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhich Linux IPC technique to use?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USRupert Swarbrick
UserOwnerUserId
1. USjschmier
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.