• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MERGEGRID issue

MyPC8MyBrain

MyPC8MyBrain

Messages
596
Country
us-california
i'm having an issues with MERGEGRID
kept cutting down jobs size to about 500 agn files at a time
i still couldn't run the jobs one after the other

i noticed memory usage doesn't get purged when the job completes
see attached image (note job end time, local clock & mem usage)



Chris,
 
Hi Chris,

Let me check, but when you run a new configuration file the memory should be cleaned. Although the .net memory management doesn't always seem to release it directly.
 
Thank you Arno

i tested few times
when the memory is purged, only a small part of it does
most times it will all remain loaded

if i start another job from the same instance,
scenProc use remaining memory, with the portion that's already been used
until an out of memory is thrown


Chris,
 
Hi Chris,

I checked the memory usage now. Here on my PC it seems the memory is not released directly after the run. Sometimes on a second run it even increases a bit more. But within 2 or 3 runs (I just ran one configuration file many times) the memory usage jumps back to low levels.

So I think what we see here is how the .NET memory management works.
 
Thank you Arno; much appreciated!

are there any step you are aware of; we can take to improve .NET performance
i searched for this info; but i couldn't find much relevant information


Best regards

Chris,
 
Hi,

I don't think we can influence how the framework works. But it should not give out of memory errors. Sometimes it just seems to release it slightly later than you would expect. But I haven't seen the memory really growing out of control.

Did you see this on xp or w7? There might be an OS difference as well. I'll try to test on xp too.
 
Thank you Arno
this issue was experience on XP; including OOM error
Windows 7 x64 was able to run the job without OOM error
but neither could complete the same job


Best egards

Chris,
 
You must log in or register to reply here.
Back
Top