Comment 2 for bug 1915761

Yes. But the problem is not the amount of memory total but rather once you exceed like 1G, ansible comes to a crawl. I'm still looking into the details but I believe it's related to fork() and python's GIL as it relates to volume of large memory objects that must be copied when a task is spawned. The reality is that our code doesn't use a fraction of the facts that we gather and things like package facts and service facts pull in a bunch of information about unrelated items which causes more problems than simply doing a targeted check