Timeline for IPC performance: Named Pipe vs Socket
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 25, 2022 at 8:42 | comment | added | shodanex | @john, also see Tim Post answer | |
| Jan 25, 2022 at 8:41 | comment | added | shodanex | If an API is more convenient for you, because it allows you to write clear code or less code, then you should use it first. Once you have a working program, with a realistic data usage, then you can evaluate the performance of your program. By evaluating it, tracing it, you can get information on where the bottleneck is. If your bottleneck is IPC speed, then you can switch to a more complicated but faster API. Given a tradeoff between speed and readability, you should pick readability first, then measure. If IPC speed is still an issue, then you can make an informed choice. | |
| Jan 24, 2022 at 7:29 | comment | added | John | "You should be sure IPC performance is a problem before preemptively optimizing." Could you please explain that in more detail? | |
| S Nov 20, 2019 at 14:21 | history | suggested | Eliahu Aaron | CC BY-SA 4.0 |
Improved spelling and grammar
|
| Nov 20, 2019 at 13:57 | review | Suggested edits | |||
| S Nov 20, 2019 at 14:21 | |||||
| Aug 6, 2009 at 13:17 | history | answered | shodanex | CC BY-SA 2.5 |