Not sure, but I suppose not.
The scheduler itselve should not have a big footprint.
I suppose there is more from application side.
You need to check which objects are use big amount of heap and whether all point to the same root-reference.
Reply to this message by going to Community
Start a new discussion in Performance Tuning at Community