Question: Lazy loading of retry fields in SQLConnection class

Do you think if it is worth moving all fields in SQLConnection class responsible for retries into a separate class worth complexity ?

I suppose retires are not so often and we can extract them in a class and only initialize it when a real retry should be done.
This will reduce memory footprint of every instance by several bytes :), but as we constantly create SQLConnections ......