{"action":"reopened","issue":{"url":"https://api.github.com/repos/s5z/zsim/issues/85","repository_url":"https://api.github.com/repos/s5z/zsim","labels_url":"https://api.github.com/repos/s5z/zsim/issues/85/labels{/name}","comments_url":"https://api.github.com/repos/s5z/zsim/issues/85/comments","events_url":"https://api.github.com/repos/s5z/zsim/issues/85/events","html_url":"https://github.com/s5z/zsim/issues/85","id":125299846,"number":85,"title":"Running server-client workload","user":{"login":"cyk0521","id":8039612,"avatar_url":"https://avatars.githubusercontent.com/u/8039612?v=3","gravatar_id":"","url":"https://api.github.com/users/cyk0521","html_url":"https://github.com/cyk0521","followers_url":"https://api.github.com/users/cyk0521/followers","following_url":"https://api.github.com/users/cyk0521/following{/other_user}","gists_url":"https://api.github.com/users/cyk0521/gists{/gist_id}","starred_url":"https://api.github.com/users/cyk0521/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cyk0521/subscriptions","organizations_url":"https://api.github.com/users/cyk0521/orgs","repos_url":"https://api.github.com/users/cyk0521/repos","events_url":"https://api.github.com/users/cyk0521/events{/privacy}","received_events_url":"https://api.github.com/users/cyk0521/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-01-07T01:08:22Z","updated_at":"2016-02-20T02:03:17Z","closed_at":null,"body":"I'm trying to analyze a complex workload that includes c++, java and python components.\r\nIn ZSim paper (ISCA'13), ZSim was used to simulate \"client-server workload that includes Java, C++ and Python components\". \r\n\r\nMy target workload is in-memory database, a server-client workload which is composed of Java/C++/Python components.\r\n\r\nBut, I got WARN message as follows when running with ZSim:\r\n\r\n[S 0] Watchdog Thread: Driving time forward to avoid deadlock on sleep (1001 -> 1018 ms)\r\n[S 0] WARN: waitUntilQueued for pid 1 tid 62 timed out\r\n...\r\n[S 0] WARN: waitUntilQueued for pid 1 tid 62 timed out\r\n[S 0] WARN: waitUntilQueued for pid 1 tid 62 timed out\r\n[S 0] Watchdog Thread: Driving time forward to avoid deadlock on sleep (2001 -> 2018 ms)\r\n[S 0] WARN: waitUntilQueued for pid 1 tid 62 timed out\r\n[S 0] WARN: waitUntilQueued for pid 1 tid 62 timed out\r\n...\r\nand it seems stopped... (I watched server process enters initialize step, but no initialization complete message.. )\r\n\r\nMy process&sim config options are \r\n\r\nprocess0 = {\r\n  command = \"bash run-test.sh server\";\r\n  process0 = {\r\n  };\r\n};\r\nsim = {\r\n  maxTotalInstrs = 10000000000000L;\r\n  logToFile = true;\r\n  phaseLength = 10000;\r\n  statsPhaseInterval = 10000;\r\n};\r\n\r\nIs there any guide document for executing client-server workloads? (cfg file structure / command option etc.)\r\nOr some efficient methods of detecting/avoiding deadlock problems?\r\n\r\n"}}