{"push_id":874413646,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"0aae904127eae05c477b98dd45a153d7b40bbe9a","before":"b40b6b5a2488cd50f7728d4fa0b1fe32232bda03","commits":[{"sha":"0aae904127eae05c477b98dd45a153d7b40bbe9a","author":{"email":"1161135013ca74a478f4fc4de471a6f1af88f2b4@ustc.edu.cn","name":"Thomas Weise"},"message":"Improved Execute and Fitting Examples\n\nThe class Execute has been improved (or bug-fixed, if you want). It will\nnow only use a ForkJoinPool to execute jobs if the calling task already\nruns in such a pool. Otherwise it will execute jobs directly. This has\nseveral reasons, such as: It is sort of awkward to leak tasks into the\ncommon ForkJoinPool in Java 8, as some of our tasks may take very long\nand thus may stall other things going on in said pool. Moreover, if we\nwant to let our jobs creep into a ForkJoinPool while not being already\nin one, we may fail if the pool is currently shutting down. Finally,\nif we always use the pool's submit function to mark jobs for execution,\nwe may again fail if the pool is shutting down, even if we legally try\nto run the tasks if we are already in the pool. Thus, I don't do this\nanymore.\n\nThe function fitting example has been improved to provide better\nstatistics and to run its jobs in parallel.","distinct":true,"url":"https://api.github.com/repos/optimizationBenchmarking/optimizationBenchmarking/commits/0aae904127eae05c477b98dd45a153d7b40bbe9a"}]}