Memory usage post DA changes

Discuss ADFFS development versions and upcoming additions
Post Reply
JonAbbott
Posts: 1736
Joined: Thu Apr 11, 2013 12:13 pm
Location: Essex

Memory usage post DA changes

Post by JonAbbott » Fri May 03, 2013 6:23 am

One side effect I've noticed since going to a DA is it's actually increased the memory usage by up to 31k, due to the page size. Although considering the previous scenario, where you could end up with 700+kb slack in the RMA, it's trivial.

It has however got me looking at "vars", which could potentially move to the front of the DA. Moving them would have the added benefit of removing most of the auto-expansion that's going on, although it would mean a lot of code changes. Something to tackle on a modular basis in the future. The alternative is to move the local vars to their respective module code, as is done with some of the Vector handlers to avoid auto-expansion breaking them.

One thing that springs to mind is the potential to take the VIDC mode translation tables out of ADFFS and have it load a relevant one for the current monitor type...vicariously allowing us to make changes or additions without code changes going forward.

Post Reply