Repository navigation
time.clock () has very low resolution on Linux #57470
Description
| BPO | 13261 |
|---|---|
| Nosy | @vstinner |
| Files |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = <Date 2011-10-25.09:39:26.816>
created_at = <Date 2011-10-25.09:37:06.950>
labels = ['type-bug']
title = 'time.clock () has very low resolution on Linux'
updated_at = <Date 2011-10-25.09:39:26.814>
user = 'https://bugs.python.org/ellioh'bugs.python.org fields:
activity = <Date 2011-10-25.09:39:26.814>
actor = 'vstinner'
assignee = 'none'
closed = True
closed_date = <Date 2011-10-25.09:39:26.816>
closer = 'vstinner'
components = ['None']
creation = <Date 2011-10-25.09:37:06.950>
creator = 'ellioh'
dependencies = []
files = ['23515']
hgrepos = []
issue_num = 13261
keywords = []
message_count = 2.0
messages = ['146347', '146348']
nosy_count = 2.0
nosy_names = ['vstinner', 'ellioh']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue13261'
versions = ['Python 2.6', 'Python 2.7']
Activity
ellioh commentedon Oct 25, 2011
time.clock () has very poor time resolution on Linux (tested on Ubuntu 11.04).
The result of call to clock () changes once per several seconds. On the other side, on Windows it provides very good resolution.
Currently on Linux I am using a workaround that is attached to the issue.
vstinner commentedon Oct 25, 2011
This issue is a duplicate of the issue bpo-10278.