Skip to content

Change Parallel to use Environment.TickCount64#87800

Merged
stephentoub merged 2 commits intodotnet:mainfrom
stephentoub:parallelforoverflow
Jun 20, 2023
Merged

Change Parallel to use Environment.TickCount64#87800
stephentoub merged 2 commits intodotnet:mainfrom
stephentoub:parallelforoverflow

Conversation

@stephentoub
Copy link
Copy Markdown
Member

Avoid wraparound issues from using Environment.TickCount.

Fixes #87543

Avoid wraparound issues from using Environment.TickCount.
@ghost
Copy link
Copy Markdown

ghost commented Jun 20, 2023

Tagging subscribers to this area: @dotnet/area-system-threading-tasks
See info in area-owners.md if you want to be subscribed.

Issue Details

Avoid wraparound issues from using Environment.TickCount.

Fixes #87543

Author: stephentoub
Assignees: stephentoub
Labels:

area-System.Threading.Tasks

Milestone: -

…ding/Tasks/TaskReplicator.cs

Co-authored-by: Dan Moseley <danmose@microsoft.com>
@stephentoub stephentoub merged commit 4198ed7 into dotnet:main Jun 20, 2023
@stephentoub stephentoub deleted the parallelforoverflow branch June 20, 2023 15:53
@danmoseley
Copy link
Copy Markdown
Member

Is this something we should consider a backport of?

@stephentoub
Copy link
Copy Markdown
Member Author

Is this something we should consider a backport of?

It's been like this for over a decade (since the .NET Native days before .NET Core), with only one report of it to my knowledge. I don't think it meets the bar.

@ghost ghost locked as resolved and limited conversation to collaborators Jul 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Parallel.For performance degrades significantly after 2.14 billion milliseconds of system uptime

3 participants