3 ms·
Why should I use MTuner as opposed to Valgrind Massif or Heaptrack? Edit: some links: https://milostosic.github.io/MTuner/overview/why/ https://milostosic.gith
by the-smug-one 3y ago
Why should I use MTuner as opposed to Valgrind Massif or Heaptrack?
Edit: some links: https://milostosic.github.io/MTuner/overview/why/ https://milostosic.github.io/MTuner/overview/why/ https://milostosic.github.io/MTuner/overview/how/ https://milostosic.github.io/MTuner/overview/how/
- forrestthewoods 3y agoValgrind and Heaptrack don't support Windows. MTuner doesn't support Linux. I'm not sure how the feature set compares MTuner. It looks like MTuner has a much richer and robust GUI for exploring the data. I'm not sure if it's intrinsically more capable. But it's certainly more user friendly and accessible!
- GuB-42 3y agoIn addition, Valgrind is based on a VM and is very slow (a 10x slowdown is typical). MTuner is based on code injection and is presumably much faster. Valgrind approach has the advantage of being very reliable, flexible, and able to run software unmodified. It has many tools (sanitizers, profilers, ...) and they are all best in class. They typically don't offer GUIs but there are external visualizers. It biggest disadvantage, besides not supporting Windows is that it is awfully slow, so much that it is generally unacceptable for user acceptance testing, let alone production, and sometimes, it is effectively not usable at all. If it is like other memory debuggers I have used (ex: dmalloc), it is fast enough for normal use, but not as exhaustive, and sometimes a bit finnicky.
- anta40 3y ago"besides not supporting Windows..." well don't forget macOS. definitely needs more contributors :D