{"action":"created","issue":{"url":"https://api.github.com/repos/FTSRG/trainbenchmark-ttc/issues/4","labels_url":"https://api.github.com/repos/FTSRG/trainbenchmark-ttc/issues/4/labels{/name}","comments_url":"https://api.github.com/repos/FTSRG/trainbenchmark-ttc/issues/4/comments","events_url":"https://api.github.com/repos/FTSRG/trainbenchmark-ttc/issues/4/events","html_url":"https://github.com/FTSRG/trainbenchmark-ttc/issues/4","id":69803732,"number":4,"title":"Add some warmup phase","user":{"login":"tsdh","id":103854,"avatar_url":"https://avatars.githubusercontent.com/u/103854?v=3","gravatar_id":"","url":"https://api.github.com/users/tsdh","html_url":"https://github.com/tsdh","followers_url":"https://api.github.com/users/tsdh/followers","following_url":"https://api.github.com/users/tsdh/following{/other_user}","gists_url":"https://api.github.com/users/tsdh/gists{/gist_id}","starred_url":"https://api.github.com/users/tsdh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tsdh/subscriptions","organizations_url":"https://api.github.com/users/tsdh/orgs","repos_url":"https://api.github.com/users/tsdh/repos","events_url":"https://api.github.com/users/tsdh/events{/privacy}","received_events_url":"https://api.github.com/users/tsdh/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2015-04-21T10:14:46Z","updated_at":"2015-04-30T19:59:56Z","closed_at":"2015-04-25T18:25:48Z","body":"When I run my solution in its standalone project, it runs much faster than when it's run by this benchmark framework.  I'm not sure what's causing this but one culprit could be that the benchmark framework runs every single test in its own new JVM instance and thus it's possible that the benchmark results are forged by just-in-time compilation.  For that reason, I'd suggest to add some warmup phase, e.g., performing the selected rule to the smallest model 10 times before measuring the concrete execution time with the current selected model.\r\n\r\nI suspect this is not the only factor, though.  I've never seen the reference clearing queue deadlock the README also speaks of now before.  It doesn't happen with any java version/variant (7 or 8, Oracle or OpenJDK) for my standalone solution (or any other project I've worked on), but I get it pretty consistently with the benchmark project as soon as I use something different than the Oracle JDK in version 7.  And the hangs/deadlocks don't occur only when running my solution but at least the java solution causes them, too."},"comment":{"url":"https://api.github.com/repos/FTSRG/trainbenchmark-ttc/issues/comments/97950901","html_url":"https://github.com/FTSRG/trainbenchmark-ttc/issues/4#issuecomment-97950901","issue_url":"https://api.github.com/repos/FTSRG/trainbenchmark-ttc/issues/4","id":97950901,"user":{"login":"dwagelaar","id":240280,"avatar_url":"https://avatars.githubusercontent.com/u/240280?v=3","gravatar_id":"","url":"https://api.github.com/users/dwagelaar","html_url":"https://github.com/dwagelaar","followers_url":"https://api.github.com/users/dwagelaar/followers","following_url":"https://api.github.com/users/dwagelaar/following{/other_user}","gists_url":"https://api.github.com/users/dwagelaar/gists{/gist_id}","starred_url":"https://api.github.com/users/dwagelaar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dwagelaar/subscriptions","organizations_url":"https://api.github.com/users/dwagelaar/orgs","repos_url":"https://api.github.com/users/dwagelaar/repos","events_url":"https://api.github.com/users/dwagelaar/events{/privacy}","received_events_url":"https://api.github.com/users/dwagelaar/received_events","type":"User","site_admin":false},"created_at":"2015-04-30T19:59:56Z","updated_at":"2015-04-30T19:59:56Z","body":"I think the 300 sec timeout used to be per run of a given task/size, and is now cumulative for all runs. So more runs = less time to complete each run."}}