Is there any way to limit the amount of memory the workflow service has access to?

It always want to sit on memory and slowly gobble up more instead of using what it already has.

Even when no workflows are running and everything is history in the database it will just sit on 4GB of memory, then when it wants more, instead of re-purposing the 4GB, it will just take more away from other systems including the OS and it's own API.

I would prefer if memory is only used for active data being processed by the CPU, and anything we are done with should be stored in the database or in ProgramData which is disk storage.

But even if I could just limit the amount it has access to, at least that would force it to stick with it's own set, instead of stealing from other services.