{"push_id":855060097,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"e89e5b253cf74b680f2c1ad3e97f3807c9634856","before":"ae7940b6282b74943ab2680a5bc5eaf887ea59f3","commits":[{"sha":"3277d172bacf2a38343f3393898cc49d79e6208e","author":{"email":"40bc6d3c318538862cbe0610c762785daf6403c0@microsoft.com","name":"Dmitri Smirnov"},"message":"Improve concurrency when running tests\n  PowerShell seems to have a hard time when a flood of async tasks is\n  scheduled at the same time.\n  I speculated that WaitForMultipleObjects() in Windows can only take up\n  to 64 process handles and if you want to handle more than you should write\n  some additional code which can be sub-optimal. I.e to implement Wait-Job -Any.\n  I decided to test that suggestion and introduced a $Concurrency parameter with a default value of 62.\n  So in the new version the script fires up up to $Concurrency value\n  and wait for anything to complete before starting any more processes.\n  This improved matters greatly. Individual tests against ramdrive now\n  run in 8 minutes and all of the 200+ db_tests run in 9 minutes with concurrency\n  values of 8-16. About 48 is required to load a CPU on my box running against HD\n  but that does not improve running times much.\n\n  Other changes include respect -EnableJE for the individual test exes.\n  Enforce exclusions for the individual tests.","distinct":true,"url":"https://api.github.com/repos/facebook/rocksdb/commits/3277d172bacf2a38343f3393898cc49d79e6208e"},{"sha":"e89e5b253cf74b680f2c1ad3e97f3807c9634856","author":{"email":"73f7a2f5b9bd744ab54cd1d307975868fc93a844@fb.com","name":"Islam AbdelRahman"},"message":"Merge pull request #818 from yuslepukhin/improve_test_concurrency\n\nImprove concurrency when running tests","distinct":true,"url":"https://api.github.com/repos/facebook/rocksdb/commits/e89e5b253cf74b680f2c1ad3e97f3807c9634856"}]}