64-bit Ryzom?

[norik0]

Just curious, are there any plans to ever have a 64-bit executable for Ryzom, on any platform?

For that matter, can one be made using the source?

[prozacr]

I think core version already fixed and compiles on 64bit Linux. Oficial build should be ready soner or later.

[norik0]

Thanks for the response! Compiling a binary from source seems extremely intensive on computer resources, so I'll just wait for the official 64-bit binary. In the mean time, I'll try to use the 32-bit compatibility libraries, even if they're not optimal for the task, especially considering the game itself is comp intensive to run at reasonable quality.

[prozacr]

>Compiling a binary from source seems extremely intensive on computer resources
You need to do this once and it sends CPU to 100% load for few minutes, not so much really. And final result is program heavily optimized for your CPU model so it runs much faster and saves resources.

[prozacr]

No edit...!?
Compiling a binary from source has only one disadwantage many ppl may lack IT skill to do it.

[norik0]

I don't know what kind of computer you have, but mine has it's limits, and yet it's pretty powerful (I have yet to find a game I can't run, even through Wine, that's not due to Wine functionality issues). I usually run " make -j4 " while compiling, but apparently 2 GB RAM, plus 1 GB swap, is nowhere near enough to handle this.

With just " make ", it takes well over 1 hour and I end up getting:

/usr/lib64/gcc/x86_64-slackware-linux/4.3.3/../../../../lib64/libwwwapp.so: undefined reference to `HTCacheAppend'
collect2: ld returned 1 exit status
make[2]: *** [bin/ryzom_client] Error 1
make[1]: *** [ryzom/client/src/CMakeFiles/ryzom_client.dir/all] Error 2
make: *** [all] Error 2

Personally, that kinda puts me off trying for quite a while... it ain't easy working with something that has to take so long to compile... : /

[prozacr]

Compile is not related to ram at all it just uses CPU and write to HDD.
It looks like you detected mistake in code as I see what you get. You should report to bugs.

[norik0]

Originally Posted by prozacr

Compile is not related to ram at all it just uses CPU and write to HDD.
It looks like you detected mistake in code as I see what you get. You should report to bugs.

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.

I submitted a bug report now.

[blaah]

Originally Posted by norik0

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)

    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.