5 ms·
Honest question here - does this document start at a point where you've already done some analysis, and decided that memory is your bottleneck, and memory profi
by danielbarla 6y ago
Honest question here - does this document start at a point where you've already done some analysis, and decided that memory is your bottleneck, and memory profiling and optimisation is the way you want to go? Or is a generally accepted best practice to first do this anyways, and then move on to e.g. CPU profiling, regardless of being say CPU-bound? I've only skimmed the document, intending to read it later, but didn't see an answer to this. Where can I find more info?
(I'm asking as someone who has done a fair bit of "performance work" but strictly at a higher level - by selecting more appropriate algorithms for the nature and size of data, minimising time spent waiting for network calls, etc, so it's rare that I have to dive very deeply in to "proper" performance work. But, I would like to learn more.)
- TruffleMuffin 6y agoPretty sure this is the person who is one of the architects on the Garbage Collector in NET.
- pjmlp 6y agoAnd a very good at it.
- danielbarla 6y agoI'm in no way questioning their expertise; I am simply asking if there's a step that comes before this document.
- ygra 6y agohttps://github.com/Maoni0/mem-doc/blob/master/doc/.NETMemoryPerformanceAnalysis.md#know-when-to-worry https://github.com/Maoni0/mem-doc/blob/master/doc/.NETMemory... probably answers your question.
- danielbarla 6y agoAh, excellent, thanks. I think this part is quite clear, also clarifying my related question, which is what the scope of this document would be: > When the relevant GC metrics says GC is having a small effect, it would be more productive to focus your effort elsewhere. If they indicate GC does have a big impact, this is when you should start worrying about how to do managed memory analysis, which is what the majority of this doc is about.