Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[goffrie]

Or you want more than about 3.5 gigs of usable memory.

DF is still 32-bit, a 64-bit OS won't help DF use any more memory.

If you have a 32 bit OS the system can only identify 4gigs worth of addresses minus everything else that is addressed on your system.  Leaving most systems with about 3.5 gigs.  I'm using 2.5 gigs idle which would leave with only 1 gig for any extra game/application.  Because I have 64 bit I have 8 gigs of addressable memory, and leaves a full 5.5 for anything extra I want to do such as DF.

DF can't use all of that 5.5 GB, though.

[Draco18s]

Or you want more than about 3.5 gigs of usable memory.

DF is still 32-bit, a 64-bit OS won't help DF use any more memory.

If you have a 32 bit OS the system can only identify 4gigs worth of addresses minus everything else that is addressed on your system.  Leaving most systems with about 3.5 gigs.  I'm using 2.5 gigs idle which would leave with only 1 gig for any extra game/application.  Because I have 64 bit I have 8 gigs of addressable memory, and leaves a full 5.5 for anything extra I want to do such as DF.

DF can't use all of that 5.5 GB, though.

Let me re-itterate:

DF is still 32-bit, a 64-bit OS won't help DF use any more memory.

[SolarShado]

But another instance could use some of that, couldn't it? Isn't the limit per process? Or is it for the entire 32-bit subsystem?

I recall reading that back in Win9X, 16-bit apps all ran in a shared memory area (or something like that) because that's how DOS did it and I guess some apps depended on that "feature" (as i recall, this meant one poorly written app could crash the entire 16-bit sub-sys), but aren't 32-bit apps more protected from each other?

[goffrie]

But another instance could use some of that, couldn't it? Isn't the limit per process? Or is it for the entire 32-bit subsystem?

Yes, multiple instances will allow you to use all of that memory.

[jfs]

Dwarf Fortress doesn't have the /LARGEADDRESSAWARE switch in the EXE header, but if it has that, and it doesn't do strange pointer magic (storing an extra bit of information in the top bit of pointer values, for example) then it should be able to use 4 GB instead of 2 GB of memory, when running on a 64 bit Windows system, without DF being recompiled at all.
I'm going to test that now, anyone else with MS developer tools can try it too:

Code: [Select]

EDITBIN /LARGEADDRESSAWARE dwarfort.exe
Edit: It seems to work, at least no crashes yet so I'm assuming it's safe. I don't have a worldgen requiring above 2 GB yet though.

Edit 2: After going to sleep with it running, in the morning DF had simply frozen while probably using 2 GB. (I didn't get the exact number.) This flag might not work anyway.

[Draco18s]

But another instance could use some of that, couldn't it? Isn't the limit per process? Or is it for the entire 32-bit subsystem?

Yes, multiple instances will allow you to use all of that memory.

Though why you'd do that is a mystery.

[Mason11987]

Just checked this morning to see how it's going, and it crashed:

Spoiler (click to show/hide)

More data needed.  Let's run it again!

Alright, didn't hit a hard limit on years.

Still hasn't crashed again.

More years (~5.5k)
Less Figures/deaths
More Events
Less RAM

I'll see how it is tomorrow morning.

[Beeskee]

If anyone wants to post some world gen specifications I can try running the generation on a dedicated computer I have. It's not very fast but it can run a df map making session for a few days instead of folding@home.

[Devast]

I think the unasked question here is.
How badass are the badasses in a 5000 year history?

[Mason11987]

Just checked this morning to see how it's going, and it crashed:

Spoiler (click to show/hide)

More data needed.  Let's run it again!

Alright, didn't hit a hard limit on years.

Still hasn't crashed again.

More years (~5.5k)
Less Figures/deaths
More Events
Less RAM

I'll see how it is tomorrow morning.

Spoke a little too soon:

Spoiler (click to show/hide)

Comparisons:
Year:5073
Figs: 197312
Ead: 168193
Events: 5306624
RAM: 1822868K

Year: 6574
Figs: 214099
Dead: 190786
Events: 6856366
RAM: 1966804K


It doesn't look like I've ran into any hard limit, at least not based on any obvious numbers.  I'll run it again to confirm.  Then I'll try to just gen a 6k year history before ending.

[ungulateman]

My computer wouldn't last 2000 years. This is impressive.

(Yeah, I reduced worldgen size to save hard drive space.)

[Mason11987]

Just checked this morning to see how it's going, and it crashed:

Spoiler (click to show/hide)

More data needed.  Let's run it again!

Alright, didn't hit a hard limit on years.

Still hasn't crashed again.

More years (~5.5k)
Less Figures/deaths
More Events
Less RAM

I'll see how it is tomorrow morning.

Spoke a little too soon:

Spoiler (click to show/hide)

Comparisons:
Year:5073
Figs: 197312
Ead: 168193
Events: 5306624
RAM: 1822868K

Year: 6574
Figs: 214099
Dead: 190786
Events: 6856366
RAM: 1966804K


It doesn't look like I've ran into any hard limit, at least not based on any obvious numbers.  I'll run it again to confirm.  Then I'll try to just gen a 6k year history before ending.

And another failure:

Year: 3713
Figs: 156987
Dead:132321
Events:7964106
RAM: 1894720K

Spoiler (click to show/hide)

It seems it's not just about Ram, nor years, nor figures (dead or otherwise), but about events or some combination probably.

Interesting.  Now to play 31.04

[Flaede]

I've set my computer to work. For SCIENCE!

EDIT: runtime error at 1656. I think I will cull historical figures next time.

[Urist Imiknorris]

Try genning a pocket world with a 50000 year history.

[tieme]

I'm finally back from vacation.  I got back yesterday to find that dwarf fortress apparently paused while I was gone.  I'm not sure why, since it is only supposed to shut the monitor off and lock the computer.  Either way, I let them continue running for a while and both crashed.  One was 1.9xx gigs and the other was 1.8xx gigs.  They always seem to crash around the same amount of memory usage. 

Maybe with 31.04 if I get bored I'll give this another shot.  Busy for the time being though.