Timeline for Formatting a CAN bus message as a string
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 2, 2015 at 19:46 | comment | added | AdamMc331 | It is really needed. I will try to get real data, I'm just not sure how to determine at which node in the TPL dataflow it's bottlenecking at. | |
| Oct 2, 2015 at 19:42 | comment | added | Jakub Lortz | @McAdam331 Definitely try to get some real data for profiling. And identify the bottlenecks before optimizing. The solution I proposed isn't really a performance optimization - it's just a .Net best practice when working with strings. Real performance optimization will probably make your code less readable and harder to maintain. Make sure it's really needed before you do it. | |
| Oct 2, 2015 at 19:06 | comment | added | AdamMc331 | I'll try this out, as well as string builder. Any tips on how I can run a preformance benchmark on this? Because I'm plugging into an ECU and running it, I don't have a list of test messages to format, just whatever I read from the vehicle at the time. :/ Maybe I will have to pull a list of messages from one run and use them in the future for bench marks if I still have no luck. | |
| Oct 2, 2015 at 18:59 | review | First posts | |||
| Oct 2, 2015 at 19:49 | |||||
| Oct 2, 2015 at 18:59 | history | answered | Jakub Lortz | CC BY-SA 3.0 |