CERTI - Patches: patch #7704, replace local full-weight...
You are not allowed to post comments on this tracker with your current authentication level.
patch #7704: replace local full-weight processes with threads
Submitter: | Eugene Chemeritskiy <tyz> | ||
Submitted: | Fri 20 Jan 2012 05:56:00 AM UTC | ||
Category: | CERTI | Priority: | 5 - Normal |
Status: | Postponed | Privacy: | Public |
Assigned to: | None | Open/Closed: | Open |
( Jump to the original submission )
Sat 25 Aug 2012 01:15:26 PM UTC, comment #9: |
Eugene Chemeritskiy <tyz>![]() |
Sat 25 Aug 2012 12:57:28 PM UTC, comment #8: Hi Eugene,
|
Eric NOULARD <erk>![]() |
Sat 25 Aug 2012 11:43:48 AM UTC, comment #7: Eric,
|
Eugene Chemeritskiy <tyz>![]() |
Fri 24 Aug 2012 07:16:04 AM UTC, comment #6: Hi Eric,
Here I tried to express that I knew how to implement the considerably clean and correct solution in case of related waiting as well as I knew nothing about internal CERTI component communications. So I've made a kind of kludge to get the proof-of-concept multi-threaded LRC.
|
Eugene Chemeritskiy <tyz>![]() |
Tue 21 Aug 2012 12:59:29 PM UTC, comment #5: Hi Eugene,
|
Eric NOULARD <erk>![]() |
Mon 20 Aug 2012 06:41:24 AM UTC, comment #4: Hi Eric,
|
Eugene Chemeritskiy <tyz>![]() |
Thu 16 Aug 2012 10:14:14 AM UTC, comment #3: Hi Eugene,
|
Eric NOULARD <erk>![]() |
Fri 20 Jan 2012 09:32:49 AM UTC, comment #2: Hi Eric,
|
Eugene Chemeritskiy <tyz>![]() |
Fri 20 Jan 2012 07:22:28 AM UTC, comment #1: Hi Eugene,
|
Eric NOULARD <erk>![]() |
Fri 20 Jan 2012 05:56:00 AM UTC, original submission:
This patch slightly changes CERTI RTI process model in attempt to increase overall RTI performance. Currently local RTI component consists of two full-weight processes, namely RTIA and Federate process. These processes interact to each other by means of TCP or UNIX socket (UNIX pipe). This type of interaction requires a lot of repeated message representation transitions and seems not to be an optimal one. There are a lot of suitable approaches: for example using of shared memory can partially solve the issue. The same common address space benefit could be reached by means of multi-threaded program.
|
Eugene Chemeritskiy <tyz>![]() |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Eric,
Thanks for your fast reaction.
As about global write access, I will keep this in mind and double check my current branch before commits.