64 bit and wastelands ?

EDIT by AgentRev - Get extDB3 here:
https://github.com/A3Wasteland/Release_Files/raw/master/A3W_extDB3_pack.zip

ok news released today.. is this good or bad for our wasteland experience ?


see it all here


https://dev.arma3.com/post/oprep-64-bit-executables

It's more about Arma than Wasteland, normally it should not break anything in A3W.

The only thing I can think about is that extDB will probably need x64 binaries for the server.

Been trying to test out the 64 bit executable. I cannot even joint a server without getting access violation. Also BE doesn't even work with the 64 bit executable at the moment.

They have a ways to go...

@agentrev
concerning extdb - i saw that torndeco is preparing extdb3 for 64bit.
i doubt that there will be  64bit dll's for extdb2.

do you plan to upgrade your release package to extdb3?

I will, if there is recorded evidence that arma3server 64 has higher server FPS than arma3server 32 under similar load.

I'm glad to hear that. so i don't have to botch ;-)

I have seen an improvement with the new memory allocators and -hugepages added to the perf build. I think the 64 bit server will just help us not get so bogged down after 3 hours of up-time, but I really think it will help clients the most. They get a lot of memory leaks and other issues when high view distance is used with a lot of objects around.

I think it will be worth it for the server though and I will help you test anything Agent. If you can get the time and will to do this.

Okay I've did some testing with the 64bit server and client with Wasteland. First there was no database issue from what I can see. Last there were a few errors such as with serverMessage.sqf and I think this has to do with parseText. There was another one with the filterExecAttempt.sqf but I cannot remember what the error was.

There will be errors with simple fixes IMHO.

There a little improvement with the FPS but like BIS stated currently the 64 bit will improve memory allocation. I believe or hope that BIS will eventually work on their engine to take more advantage of the GPU.

Hello all,

I have tested the 64-Bit Server with the 64-Bit Client right now. (#RC)
Client FPS are much better with 64-Bit! Anyway, the server FPS are interesting:

32-Bit Server: started with 38 FPS and did not change significantly
64-Bit Server: started with 30 FPS, jumped up to 50 FPS after some minutes.

I have tested that with our dedicated Server. I measured the FPS with the ingame command "monitor" and I was alone on the server. I have compared 32-Bit (with DB) with 64-Bit (without DB) exe from current RC Branch. The 64-Bit used more memory - that may be important for stable performance over long sessions. I would really appreciate it, to change to the new extDB version. Anyway, I know it is a lot of work.

Armajunkies-Internal Ticket ID: https://armajunkies.atlassian.net/browse/AJWL-157

Staynex / Armajunkies.de

The changes required for extDB3 should be minor.
I will submit a pull request with the changes to github sometime in the next few days.

 

Thank you Torn for supporting Wasteland !

The changes required for extDB3 should be minor.
I will submit a pull request with the changes to github sometime in the next few days.

Awesome!

Thanks torndeco. Looking forward to testing this.

If someone wants to help test out the changes etc
SQF wise its just some minor tweaks

https://github.com/Torndeco/ArmA3_Wasteland.Altis/commit/814637fecbdd5c9035ad347618c071b96c0e9f7a

If there is a mistake, chances are its in the a3wasteland.ini.
This file should be simpiler now and has some error checking to catch some typo mistakes etc
http://pastebin.com/Ytgsk56T

Download @extDB3 at https://bitbucket.org/torndeco/extdb3/downloads
Don't forget to edit the extdb3-conf.ini, database section name = [A3W]   etc

-----------------------

I only tested the basics out i.e player saving / respawning / loading.
After your server is running abit, check the extdb3 log and see if there is any sql exception errors etc

Thanks

Note if you are on dev / rc build

call compile  for  extDB2/3 results  can be replaced by
https://community.bistudio.com/wiki/parseSimpleArray

This is not in the changes above, incase someone wants to test extDB3 changes on 1.66 (stable)