I wonder about how RAM is used

One thing I wonder about:

It was said that the replay file is kept in RAM (until saved after the race).

I have 8 GB RAM.

During a session with AC, I see in a graph that my system uses not all those 8GB at all, but more than the half, but still less than three quarters. I think saying it uses 5 GB of my RAM, is a fair estimation.

That leaves 3 GB RAM untouched. Even more, the virtual RAM on my HD nevertheless gets accessed. Why - if I have 3 GB RAM left?

What I am wondering about is why I cannot have longer replays than 500 MB, when I have so much RAM unused?

 

I am pretty sure AC is a 32bit application so it can only address a maximum of 4gb if ram. On 64bit apps can use more not sure if its possible for a 32bit app to use a seperate portion of memory for something like the replay filek8nd 9f like a virtual ram disk to get the total amount above 4gb. On a 64 bit Os a 32bit app can use 4gb just for itself and leave the rest for OS and background processes. If you were on a 32bit OS then the total amount of ram useable would be 4gb no matter how much you had. Currently I havent seen any need for AC to need more then 4gb other then the replay size and the limitations of this method currently used.

 

They should be being streamed to disk anyway, thereby making RAM a moot point.

 

There is a file that addresses the replay file size, and I`m pretty sure I had it set at 500 (coincidence) when the in-game limit was still 25MB.

Maybe try editing the file manually to 1000 (essentially 1GB) and see if it saves a file over 500MB? You would have to do a pretty long race though, because if my memory serves me correct, a 15 minute race took about 300MB?

 

That's because acs.exe is a 32bits executable that can only access to a maximum of 4GB of ram where 500MB of this space is reserved for replays

 

Oh, I thought it were truly 64 Bit, "next generation" and all that. 32 Bit explains it all. The additional 1-1.5 GB in use must be system-related, then.

The replay size edit in the ini does not work too well, since I did that and know it causes the maximum number of cars to drop. When fixing the replay (by mistake) in the ini to 1 hour, the game did not launch to race with more than 12 or 13 cars in the grid.

 

That depends on the number of cars in race. With 16 cars and 0.61, around 5 laps were covered. With 24 cars, at least the first third of the race already was missing. Well, roughly estimating by my memories. Obviously, it also depends on the length of track, and the speed at which the cars do one round. The more time it takes, the fewer distance the replay covers.

 

I suggested that in a thread three weeks ago or so. Staff said that doing so would mean a nightmare for the HD. I had no idea in what way that would be a nightmare for the HD, but I am technically not competent to put the programmer's reply into question.

 

I never tried editing the time limit in the ini file, so can't vouch for that, but have you tried increasing the max file size past the in-game limit?

 

This is not because of poor coding but because a lot of people are still on 32bit systems and then if it was only 64bits then a slice of market would be cutted off

 

Two, say, 50mb buffers, one being filled and one being written out in a couple of big writes on a separate thread once filled (then swap 'em over) would barely make the machine blink and wouldn't block the thread filling the current buffer for the sort of amount of time that makes game programmers wince (i.e. anything perceptible).

Voila one 2 minute "I wonder how quick it'll actually write that amount of data in one hit" bit of code...

Code:

            
for (int i = 0; i < 10; i++)
{
   byte[] buffer = new byte[1024 * 1024 * 50];

   System.IO.FileStream fileStream = new System.IO.FileStream("c:\\test.crap", System.IO.FileMode.OpenOrCreate, System.IO.FileAccess.Write);
   fileStream.Seek(0, System.IO.SeekOrigin.End);
   fileStream.Write(buffer, 0, buffer.Length);
   fileStream.Flush();
   fileStream.Close();
}

...profiled at 45ms, and 5ms of that was allocating the buffer. So that's 500MB dumped to my crappy C: drive in ten 50MB chunks in 0.045 seconds, during which time a writing thread would be asleep anyway (so that's not wholly lost time on a given core). Streaming the stuff to disk in chunks is child's play and has no performance implications beyond, er, freeing up more memory.

Okay, appending every single record in the replay to a file the moment it was created would be horribly slow, but it would also be a truly stupid solution to the problem.

Non-techy version - Nah, it's dead quick. Whoever told you that didn't have their thinking brain in.

 

I just said I did, and I just gave the description of what consequences that had! It comes at the cost of reducing the number of cars you can have in a race.

 

Just to avoid any misunderstandings, I nowhere said or implied "poor coding".

 

As I said, it was somebody official from Kunos team, Giovanni Romagnoli. See this thread from February 1st, and post #10: http://www.assettocorsa.net/forum/i...f-memory-replay-size-too-big.5914/#post-70282

Maybe he reads this and could leave a comment ?!

 

You know what, i`m having one of those days today where i`m reading bits of information and it's not sinking in!

I give up lol

 

Maybe they release someday a 64 bit exe. That would be nice, some games already use only 64 bit.

Gesendet von meinem HTC One mit Tapatalk

 

I wonder how many people are still on 32 bit os, 64 bit processors have been the only ones sold for quite a few years but its amazed me why windows dragged its butt for so long continuing with 32 bit when it can run 64 and 32 bit apps without issues in 64 bit OS. Sure driver issues was probably the main hold up but all new hardware over the last 5 to 10 years will have 64 bit drivers too.

 

It's a scary idea - especially now that MS is stopping support - but still around 30% of computers run.... Windows XP

http://gadgets.ndtv.com/laptops/new...-still-at-30-percent-despite-impending-491722

But you'd expect anyone who has the hardware to play this game with half-decent frame rate to be on 64 bit, really.

 

With the very fast and large SSD's available i believe there should be the option to save to disc rather than memory for those who are able to!

 

iRacing streams replays to disk and it's not an issue even on a HDD.

Here's a better place to look for stats on gamer systems
http://store.steampowered.com/hwsurvey

6% for XP32, 1.3% Vista32, 12% Win7 32.