Memory Usage Continuously increases- Fails to release

[Anonymous]

Using ACA 2016 on a Dell M6800 Windows 8.1 32G RAM AMD FirePro6100 Graphics card. All drivers are current. Dell has replace the M'board twice and the AMD card once in an effort to resolve performance issues.

I have tried many options to improve the performance on this machine turning off switchable graphics,toggling hardware acceleration, disabling the native Intel Graphics card, increasing page file size........- not sure if it is an OS issue, ACAD issue, graphics issue or some level of incompatibility between them.

Problems include delay in command line response (already modified the delay setting) and extended delays (Acad Not Responding) when changing views.

Most notable is the continual increase in RAM usage even when a drawing is opened and left idle; starts out at 270mb and climbs upward to 3200mb at which point the program becomes useless.

I will take any and all suggestions.

[leothebuilder]

What typical file sizes do you have problems with?

[Anonymous]

File size does not seem to be the focal point although the larger the file, obviously the harder the machine has to work. But what I am experiencing is excessive- I feel like I am working on a x386 pentium II.

Command line and view regeneration delays begin at startup and grow longer as the RAM gets consumed and not released. 

My file sizes tend to balloon out of proportion- an archived iteration of a current file is 12mb whereas the current file has (now that you make look at it) increased to 26mb with no significant amount of additional data being added.

The ever increasing RAM usage is not a product of file size; it occurs simply by opening any dwg file and increases at a rate of about .5mb every second with some minor breaks.

[leothebuilder]

If you have a basic of of 12mb that is a large file.

I've been using ACA for many years and a large file for me is around 3 or 4mb.

Most of my files are less than 1mb.

I would imagine a 12mb file would cause me some problems as well.

That does not explain the increase in file siaze when it's in use and I have no idea what would cause that.