{"issue":{"milestone":null,"user":{"id":43198,"login":"ehuss","url":"https://api.github.com/users/ehuss","avatar_url":"https://secure.gravatar.com/avatar/6740466874c04b1e9e679929b79ff111?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"6740466874c04b1e9e679929b79ff111"},"created_at":"2011-12-17T03:29:03Z","title":"Implement New Time Tracking","updated_at":"2011-12-17T03:29:03Z","labels":[],"state":"open","id":2587343,"html_url":"https://github.com/ironport/shrapnel/issues/7","closed_at":null,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"body":"Using TSC has a variety of problems.\r\n\r\n* Determining which sysctl to read to determine the TSC-to-seconds conversion is difficult.  Some systems don't even have it (My Mac Mini with Snow Leopard, Bob's Amazon FreeBSD Xen virtualized system, etc.).\r\n* Some systems do not have a reliable TSC.  We do not check for this.\r\n* There's clunky code to handle re-calibrating our relationship of TSC to wall clock.  I've never been comfortable with this.  (This was a performance hack to avoid calling gettimeofday a lot, I'm not sure how important that is.)\r\n\r\nWe need a new API for handling high-resolution time.  Preferably something that can use multiple types of time.  See https://github.com/ironport/aplib/issues/2 for more detail.\r\n\r\nPreferably, this new API would be in shrapnel to help remove the dependency with aplib.\r\n","number":7,"url":"https://api.github.com/repos/ironport/shrapnel/issues/7","comments":0,"assignee":null},"action":"opened"}