I've noticed that when we run tests in our solution, the following EXEs skyrocket in memory:
vstest.discoveryengine..x86.exe
vstest.executionengine.x86.exe
It's not easy to tell, but it seems like once the JS tests are being discovered or executed, the memory consumption goes up.
Is this something that others have seen? Our solution has about 3000 tests, 800 of which are JS tests.
Comments: I released version 3.2 (http://matthewmanela.com/blog/chutzpah-3-2-a-smarter-approach-to-compilation/) which included a new compile setting which you should use instead of the former built in compilation approach. Now you provide chutzpah with how to compile which will be faster and not hog memory like the former approach
vstest.discoveryengine..x86.exe
vstest.executionengine.x86.exe
It's not easy to tell, but it seems like once the JS tests are being discovered or executed, the memory consumption goes up.
Is this something that others have seen? Our solution has about 3000 tests, 800 of which are JS tests.
Comments: I released version 3.2 (http://matthewmanela.com/blog/chutzpah-3-2-a-smarter-approach-to-compilation/) which included a new compile setting which you should use instead of the former built in compilation approach. Now you provide chutzpah with how to compile which will be faster and not hog memory like the former approach