[BOLT-1208] SPIKE - Determine next area for Windows perf improvements Created: 2019/03/26  Updated: 2019/08/26  Resolved: 2019/08/26

Status: Closed
Project: Puppet Task Runner
Component/s: performance, Windows
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Normal
Reporter: Ethan Brown Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: closed-github-move, performance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relates to BOLT-1224 SPIKE - Investigate lighter weight co... Closed
relates to BOLT-1119 Improve Bolt startup time on Windows ... Resolved
relates to BOLT-1186 Improve Bolt startup time on Windows ... Resolved
Team: Bolt
Sprint: Bolt Ready for Grooming
QA Risk Assessment: Needs Assessment


Now that BOLT-1119 and BOLT-1186 are completed in an effort to improve startup time performance on , further investigate areas for performance improvements on Windows

  • Loading the list of available tasks / plans from modules on disk (i.e. bolt plan show and similar)
  • Connecting to remote hosts once to run a command / script / task
  • Connecting to the same host multiple times to run a command / script / task

It may be useful to get other scenarios that feel "slow" to Windows users.

Another useful output of this ticket might be a dependency graph showing how files / classes / gems are related to one another.

Comment by Lucy Wyman [ 2019/08/26 ]

This issue was automatically closed when the Bolt team moved to using Github Issues for ticket management (August 2019). If you'd like to reopen the issue or discuss it further please open a github issue at http://github.com/puppetlabs/bolt/issues.

Generated at Sun Dec 15 10:43:52 PST 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.