{"action":"created","issue":{"url":"https://api.github.com/repos/frerich/clcache/issues/229","repository_url":"https://api.github.com/repos/frerich/clcache","labels_url":"https://api.github.com/repos/frerich/clcache/issues/229/labels{/name}","comments_url":"https://api.github.com/repos/frerich/clcache/issues/229/comments","events_url":"https://api.github.com/repos/frerich/clcache/issues/229/events","html_url":"https://github.com/frerich/clcache/issues/229","id":178564966,"number":229,"title":"Lock Timeout even with 60s","user":{"login":"akleber","id":3729218,"avatar_url":"https://avatars.githubusercontent.com/u/3729218?v=3","gravatar_id":"","url":"https://api.github.com/users/akleber","html_url":"https://github.com/akleber","followers_url":"https://api.github.com/users/akleber/followers","following_url":"https://api.github.com/users/akleber/following{/other_user}","gists_url":"https://api.github.com/users/akleber/gists{/gist_id}","starred_url":"https://api.github.com/users/akleber/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/akleber/subscriptions","organizations_url":"https://api.github.com/users/akleber/orgs","repos_url":"https://api.github.com/users/akleber/repos","events_url":"https://api.github.com/users/akleber/events{/privacy}","received_events_url":"https://api.github.com/users/akleber/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-09-22T09:45:21Z","updated_at":"2016-09-26T14:48:41Z","closed_at":null,"body":"Before starting to work on the lockfile based locking again, I wanted to see how clcache has evolved since 3.0.3. Also I wanted to get some reference timing data for later comparison with another locking strategy and also wanted to use it on our internal main project.\r\nWe have a build driven by ninja (generated by cmake). I am testing on a 4 core VM so there should be at max 4 clcache instances running at the same time. I am using the 3.3.0 release. A complete build generates about 6500 cache entries.\r\nDuring the build I get a Lock Timeout Error with the 10s default timeout value and even with a 60s timeout.\r\nI then activated profiling to see where the time might be spent. But with profiling on I am not getting any timeouts. The profiling result of a completed run is attached. [prof.txt](https://github.com/frerich/clcache/files/486913/prof.txt)\r\nAny hints on how to diagnose this further? I started looking at the clcache code but it seams that much has changed since I last looked at the code."},"comment":{"url":"https://api.github.com/repos/frerich/clcache/issues/comments/249592191","html_url":"https://github.com/frerich/clcache/issues/229#issuecomment-249592191","issue_url":"https://api.github.com/repos/frerich/clcache/issues/229","id":249592191,"user":{"login":"akleber","id":3729218,"avatar_url":"https://avatars.githubusercontent.com/u/3729218?v=3","gravatar_id":"","url":"https://api.github.com/users/akleber","html_url":"https://github.com/akleber","followers_url":"https://api.github.com/users/akleber/followers","following_url":"https://api.github.com/users/akleber/following{/other_user}","gists_url":"https://api.github.com/users/akleber/gists{/gist_id}","starred_url":"https://api.github.com/users/akleber/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/akleber/subscriptions","organizations_url":"https://api.github.com/users/akleber/orgs","repos_url":"https://api.github.com/users/akleber/repos","events_url":"https://api.github.com/users/akleber/events{/privacy}","received_events_url":"https://api.github.com/users/akleber/received_events","type":"User","site_admin":false},"created_at":"2016-09-26T14:48:41Z","updated_at":"2016-09-26T14:48:41Z","body":"Sorry I forgot to mention that it always is this message:\r\n`Failed to acquire lock <...> after 60000ms; try setting CLCACHE_OBJECT_CACHE_TIMEOUT [..]`\r\n\r\nThe timeout does unfortunately not occur at the same place/progress during compilation. The machine is a VM and so fluctuations are expected.\r\nWith the 60s timeout and with profiling on the cold cache build without #230 took 117m, the build with the patch took 123m. So assuming a 5% measurement uncertainty the build took the same amount of time.\r\nBTW: I am using Pytnon 3.5.1 32bit.\r\n\r\n"}}
{"actor":{"display_login":"akleber"}}