64-bit Ryzom?

[blaah]

Actually, it is related to RAM. Dang if I could find exactly how (I'm guessing the compiled executable and some of the processed code is passed into RAM), but you better give me a really good explanation as to why my computer runs out of RAM really quick and even freezes when I run make -j4, and only uses about maximum 25% of RAM without any multi-threading options.

500MB-600MB for single compile thread sounds about right. -j4 uses 4 times as much. stall/freeze probably means that there is heavy swaping.

runned clean '/usr/bin/time -v make -j4' to compile NeL and Ryzom Client (nel test/tool off, server off)

Code: Select all

    User time (seconds): 3864.16
    System time (seconds): 257.23
    Percent of CPU this job got: 363%
    Elapsed (wall clock) time (h:mm:ss or m:ss): 18:54.76
    Average shared text size (kbytes): 0
    Average unshared data size (kbytes): 0
    Average stack size (kbytes): 0
    Average total size (kbytes): 0
    Maximum resident set size (kbytes): 3717824
    Average resident set size (kbytes): 0
    Major (requiring I/O) page faults: 106
    Minor (reclaiming a frame) page faults: 58953914
    Voluntary context switches: 211673
    Involuntary context switches: 747934
    Swaps: 0
    File system inputs: 300688
    File system outputs: 13546128
    Socket messages sent: 0
    Socket messages received: 0
    Signals delivered: 0
    Page size (bytes): 4096
    Exit status: 0

if I read this correctly, then peak memory was 3.7G. for C++ project it's normal.