Skip to content

Update potential-pitfalls-in-data-and-task-parallelism.md - Remove reference to 'cust.Orders' that doesn't apply #43669

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gewarren merged 1 commit into from
Nov 21, 2024
Merged

Update potential-pitfalls-in-data-and-task-parallelism.md - Remove reference to 'cust.Orders' that doesn't apply #43669

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...tandard/parallel-programming/potential-pitfalls-in-data-and-task-parallelism.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ In many cases, <xref:System.Threading.Tasks.Parallel.For%2A?displayProperty=name

- You are performing an expensive computation on each order. (The operation shown in the example is not expensive.)

- The target system is known to have enough processors to handle the number of threads that will be produced by parallelizing the query on `cust.Orders`.
- The target system is known to have enough processors to handle the number of threads that will be produced by parallelizing the processing.

In all cases, the best way to determine the optimum query shape is to test and measure.

Expand Down
Loading