search

pylint-bot / test

0 stars 0 forks source link

Memory implications of adding information to Uninferable #237

Open pylint-bot opened 8 years ago

pylint-bot commented 8 years ago

Originally reported by: BitBucket: ceridwenv, GitHub: @ceridwen?

For debugging purposes, along with the structured exceptions #189, I'd like to add information to Uninferable objects, but this could increase the memory demands of inference too much. I need to check to see how much memory the added information consumes.

pylint-bot commented 8 years ago

Original comment by BitBucket: ceridwenv, GitHub: @ceridwen?:

What would be a good benchmark for determining memory consumption of inference? I was thinking about it and realized that astroid probably uses less memory when testing inference than pylint does when using it, so the test should probably be done with pylint. That said, what would be the right thing to run pylint on? Do you have any memory-intensive code bases you regularly use pylint on? My current plan involves the use of the Python 3.4 stdlib tracemalloc and maybe trying to count how many times inference objects are created. I also think I'm going to split this out from the structured_exceptions patch.

pylint-bot commented 8 years ago

Original comment by Claudiu Popa (BitBucket: PCManticore, GitHub: @PCManticore?):

Indeed, testing this with astroid might not provide enough statistical value in order to draw a relevant conclusion. I usually run pylint over https://github.com/openstack/nova, since it's quite big and a minimal difference in speed can be easily noticed with its magnitude.