TaskScheduler.hwm default to 1 instead of 0 #1294

Merged
merged 2 commits into from Jan 20, 2012

Conversation

Projects
None yet
2 participants
@minrk
Member

minrk commented Jan 20, 2012

1 has more predictable/intuitive behavior, if often slower, and thus a more logical default.

closes #1293

minrk added some commits Jan 19, 2012

change TaskScheduler.hwm default to 1 from 0
0 should be considered an optimization, and 1 is less likely to confuse new users.

fperez added a commit that referenced this pull request Jan 20, 2012

Merge pull request #1294 from minrk/hwm1
TaskScheduler.hwm default to 1 instead of 0.  1 has more predictable/intuitive behavior, if often slower, and thus a more logical default.  Users whose workloads require maximum throughput and are largely homogeneous in time per task can make the optimization themselves, but now the behavior will be less surprising to new users.

closes #1293

@fperez fperez merged commit 0cde7de into ipython:master Jan 20, 2012

@fperez

This comment has been minimized.

Show comment
Hide comment
@fperez

fperez Jan 20, 2012

Member

Great, thanks. Just merged.

Member

fperez commented Jan 20, 2012

Great, thanks. Just merged.

mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this pull request Nov 3, 2014

Merge pull request #1294 from minrk/hwm1
TaskScheduler.hwm default to 1 instead of 0.  1 has more predictable/intuitive behavior, if often slower, and thus a more logical default.  Users whose workloads require maximum throughput and are largely homogeneous in time per task can make the optimization themselves, but now the behavior will be less surprising to new users.

closes #1293
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment