Timeline for Best way for memory to pass method parameters
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 24, 2016 at 0:15 | comment | added | Mike Johnson | passing individual properties is going to be even worse if you think it's bad now. When you pass the object as a whole, you are sending a reference to it (basically c#'s version of a pointer) so one reference. If you send multiple properties instead, you're sending several references + some value copies (DateTime, bool). Any performance bottleneck you are experiencing must be coming from something else. | |
| Jan 22, 2016 at 19:13 | vote | accept | Clock | ||
| Jan 21, 2016 at 19:40 | comment | added | D Stanley |
Timing your app using StopWatch is not an effective way to find performance issues. It can be a decent way to compare algorithms but it requires MANY iterations to give menaingful results. Cosider looking at commercial profilers like Ants or dotTrace to get a more accurate understanding of possible performance issues. Passing parameters is very likely not one of your problems.
|
|
| Jan 21, 2016 at 19:37 | comment | added | jgauffin | time is money, not memory. | |
| Jan 21, 2016 at 19:13 | answer | added | Sergey Kalinichenko | timeline score: 4 | |
| Jan 21, 2016 at 19:08 | comment | added | Clock | Yes, I was using a StopWatch instance to count the running time, and was bigger... | |
| Jan 21, 2016 at 19:04 | comment | added | AlG | How did you determine you were having memory issues due to parameter passing? Have you done a performance/memory analysis of your app? | |
| Jan 21, 2016 at 19:03 | answer | added | Markus Weninger | timeline score: 1 | |
| Jan 21, 2016 at 18:59 | history | asked | Clock | CC BY-SA 3.0 |