Changes between Version 1 and Version 2 of WikiStart


Ignore:
Timestamp:
06/03/15 16:37:30 (9 years ago)
Author:
hfinkel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v1 v2  
    1 = Welcome to Trac 0.11.7 = 
     1= ALCF memlog = 
    22 
    3 Trac is a '''minimalistic''' approach to '''web-based''' management of 
    4 '''software projects'''. Its goal is to simplify effective tracking and handling of software issues, enhancements and overall progress. 
     3This tool attempts to help you answer the question: Why is my application using so much memory? 
    54 
    6 All aspects of Trac have been designed with the single goal to  
    7 '''help developers write great software''' while '''staying out of the way''' 
    8 and imposing as little as possible on a team's established process and 
    9 culture. 
     5Why was memlog created? There are several other tools that can support this use 
     6case, but none of them would work in our environment properly. They were 
     7either too slow, not runnable under the BG/Q CNK, not thread safe, did not 
     8properly support big-endian PPC64, supported only either static or dynamic 
     9linking, did not collect full backtraces, or just did not produce 
     10sufficiently-informative peak-usage output. 
    1011 
    11 As all Wiki pages, this page is editable, this means that you can 
    12 modify the contents of this page simply by using your 
    13 web-browser. Simply click on the "Edit this page" link at the bottom 
    14 of the page. WikiFormatting will give you a detailed description of 
    15 available Wiki formatting commands. 
     12That having been said, memlog works quite well on my laptop in addition to working on our supercomputers. 
    1613 
    17 "[wiki:TracAdmin trac-admin] ''yourenvdir'' initenv" created 
    18 a new Trac environment, containing a default set of wiki pages and some sample 
    19 data. This newly created environment also contains  
    20 [wiki:TracGuide documentation] to help you get started with your project. 
     14If memlog does not quite do what you'd like, here are some other tools that might fit your needs: 
    2115 
    22 You can use [wiki:TracAdmin trac-admin] to configure 
    23 [http://trac.edgewall.org/ Trac] to better fit your project, especially in 
    24 regard to ''components'', ''versions'' and ''milestones''.  
     16 * Valgrind Massif - http://valgrind.org/docs/manual/ms-manual.html 
     17 * Google Performance Tools - http://google-perftools.googlecode.com/svn/trunk/doc/heapprofile.html 
     18 * memtrail - https://github.com/jrfonseca/memtrail 
     19 * LeakTracer - http://www.andreasen.org/LeakTracer/ 
     20 * glibc mtrace - http://www.gnu.org/s/hello/manual/libc/Allocation-Debugging.html 
     21 * Heaptrack - http://milianw.de/blog/heaptrack-a-heap-memory-profiler-for-linux 
     22 * MemProf - http://www.secretlabs.de/projects/memprof/ 
    2523 
     24The dot/pdf output produced by memlog was definitely inspired by that produced 
     25by Google's pprof tool in the aforementioned package. 
    2626 
    27 TracGuide is a good place to start. 
    28  
    29 Enjoy! [[BR]] 
    30 ''The Trac Team'' 
    31  
    32 == Starting Points == 
    33  
    34  * TracGuide --  Built-in Documentation 
    35  * [http://trac.edgewall.org/ The Trac project] -- Trac Open Source Project 
    36  * [http://trac.edgewall.org/wiki/TracFaq Trac FAQ] -- Frequently Asked Questions 
    37  * TracSupport --  Trac Support 
    38  
    39 For a complete list of local wiki pages, see TitleIndex.