Hi @spalladino, thanks for reaching out.
As a curiosity: where did you get the suggestion of running ganache with that flag?
This is (or was? maybe not any more) a “best practise” that I have learned how to deal with Ganache in order to speed up the development of smart contracts, “best practice” at least back then 2 years ago.
When you google the term “gas limit” and “0xffffff…” you’ll find several GitHub issues, where developers are suggesting it, or READMEs or Stackoverflow questions and answers, where this is part of setup instructions. And tutorials mentioning it. I have found this 1 til 2 years ago after looking for a solution of permanent “out of gas”-exceptions with every single function that was added to the smart contract.
I am completely with you, that this is not the best pattern but would close our developer eyes against to real gas consumption on a main network.
But it allows us to develop against any requirement that we’ve got without to spent too much time on gas consumption. I know, that this could be an issue later on deployment on main net.
How do you deal with it? And with raising gas consumption running lots of tests?