Valgrind then executes that program under a "synthetic CPU" all the code being run is instrumented. The user executes Valgrind, providing the name of the executable of interest as a parameter. Being smart with your data layout and access can have phenomenal results. Having to fetch data from the slow memory is a "cache miss", and it takes a lot longer than fetching the data from the fast memory (the "cache"). Small amounts of fast memory, large amounts of slow memory, and sometimes layers inbetween. ![]() Cache misses - this being the future, there are levels of memory.If you leak away all your memory, and start using swap space, performance turns to sludge. Memory leaks - memory leaks render memory unavailable for reuse.Valgrind is a suite of simple, command-line tools (if you run valgrind without specifying which tool, you get the default memcheck tool) that enables you to identify a whole lot of things, of which the following are especially interesting to us in terms of performance:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |