Project

General

Profile

Feature #24112

Add warning to autotune tooltip

Added by Dave F over 4 years ago. Updated over 3 years ago.

Status:
Done
Priority:
Expected
Assignee:
Timothy Moore II
Category:
GUI (new)
Estimated time:
Severity:
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

Description

Seen various posts in the forum recently regarding the autotune feature in FreeNAS. Majority of the time, an uninformed user of FreeNAS enables this feature believing it to be a magical option to fine tune their system for optimal performance. In reality, it does nothing but cause headaches for the end user, usually resulting in poor performance. Please can the autotune feature be hidden, or at least a HUGE RED WARNING informing the end user this may degrade performance?

Just a couple of examples (old and new forum posts) where it's impacted performance:
https://forums.freenas.org/index.php?threads/during-large-transfer-speed-drops-by-about-60-and-cannot-browse-web.54716
https://forums.freenas.org/index.php?threads/autotune-settings-negative-read-impact.19153/
https://forums.freenas.org/index.php?threads/performance-reduced-from-60-to-10mb-s-after-switching-autotune-on-off.11553/


Related issues

Related to FreeNAS - Bug #27502: webui/src/app/pages/system/advanced/advanced.component.ts mismatch with other UI filesDone2017-12-29
Related to FreeNAS - Bug #28132: iSCSI poor performance after 12-24 hoursClosed2018-02-01

History

#1 Updated by William Grzybowski over 4 years ago

  • Status changed from Unscreened to Screened
  • Target version set to 11.1

#2 Updated by William Grzybowski almost 4 years ago

  • Target version changed from 11.1 to 11.2-BETA1

#3 Updated by William Grzybowski almost 4 years ago

  • Status changed from Screened to Closed: Not To Be Fixed
  • Target version changed from 11.2-BETA1 to N/A

We have decided to not remove it.

Yes, it can tank performance in some cases but it can also help. We will rather try to improve it for now.

#4 Updated by Dave F almost 4 years ago

Could the feature be better documented in this case instead of closing the ticket? Having a paragraph on when to and when not to use autotune would be helpful.

#5 Updated by William Grzybowski almost 4 years ago

  • Status changed from Closed: Not To Be Fixed to Unscreened
  • Assignee changed from William Grzybowski to Dru Lavigne

Dru, Any thoughts on this? Regarding doc of autotune?

#6 Updated by Dru Lavigne almost 4 years ago

  • Assignee changed from Dru Lavigne to William Grzybowski

Currently the docs say: FreeNAS® provides an autotune script which optimizes the system depending on the installed hardware. For example, if a ZFS volume exists on a system with limited RAM, the autotune script automatically adjusts some ZFS sysctl values in an attempt to minimize ZFS memory starvation issues. It should only be used as a temporary measure on a system that hangs until the underlying hardware issue is addressed by adding more RAM. Autotune will always slow such a system, as it caps the ARC.

What else would we want to say?

#7 Updated by William Grzybowski almost 4 years ago

  • Category changed from 2 to GUI (new)
  • Assignee changed from William Grzybowski to Anonymous

Ok, as far as I can see documentation looks reasonable.

Erin, what do you think about adding some note similar to the docs in the new UI?

#8 Updated by Dru Lavigne almost 4 years ago

  • Status changed from Unscreened to Screened
  • Assignee changed from Anonymous to Dru Lavigne
  • Target version changed from N/A to 11.2-BETA1

We'll add a warning when writing the tooltip.

#9 Updated by Dru Lavigne almost 4 years ago

  • Subject changed from Remove autotune to Add warning to autotune tooltip

#10 Updated by Dru Lavigne over 3 years ago

  • Status changed from Screened to Not Started
  • Assignee changed from Dru Lavigne to Timothy Moore II

Tim: please check that the new UI tooltip is correct.

#11 Updated by Timothy Moore II over 3 years ago

  • Status changed from Not Started to Blocked
  • Reason for Blocked set to Dependant on a related task to be completed

Waiting for resolution of an issue with the System/Advanced page not supporting tooltips like the other new UI files.

#12 Updated by Timothy Moore II over 3 years ago

  • Related to Bug #27502: webui/src/app/pages/system/advanced/advanced.component.ts mismatch with other UI files added

#13 Updated by Timothy Moore II over 3 years ago

  • Status changed from Blocked to In Progress
  • Priority changed from Nice to have to Expected
  • Target version changed from 11.2-BETA1 to Master - FreeNAS Nightlies
  • % Done changed from 0 to 100
  • Reason for Blocked deleted (Dependant on a related task to be completed)

Opened pull request #374 in freenas/webui (https://github.com/freenas/webui/pull/374) to resolve this issue.

#14 Updated by Dru Lavigne over 3 years ago

  • Status changed from In Progress to Done
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#15 Updated by Dru Lavigne over 3 years ago

  • Related to Bug #28132: iSCSI poor performance after 12-24 hours added

Also available in: Atom PDF