CLI commands seem to running quite a bit slower now

[SCWells72]

Summary

Has something changed recently with the CLI such that commands might be running considerably slower? I've noticed it with simple commands such as config set but also specifically with any command that needs to refresh the OAuth token. And it's not just something that I'm seeing personally, but I'm also starting to hear about it from users of Illuminated Cloud when it runs CLI commands, specifically at the beginning of the work day and the OAuth token is stale and needed to be refreshed.

I spoke with another dev at Salesforce who mentioned that they are also seeing OAuth to be slower even for connected apps, so perhaps it's not a CLI issue but something with server-side OAuth handling?

Anyway, I ask because it seems like CLI execution had gotten into a quite decent state up until a few months ago, and then it started to degrade quite noticeably again. Any insights?

System Information

{
  "architecture": "win32-arm64",
  "cliVersion": "@salesforce/cli/2.68.6",
  "nodeVersion": "node-v20.17.0",
  "osVersion": "Windows_NT 10.0.26100",
  "rootPath": "C:\\Users\\Scott\\AppData\\Roaming\\npm\\node_modules\\@salesforce\\cli",
  "shell": "cmd.exe",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.10 (core)",
    "@oclif/plugin-commands 4.1.10 (core)",
    "@oclif/plugin-help 6.2.18 (core)",
    "@oclif/plugin-not-found 3.2.28 (core)",
    "@oclif/plugin-plugins 5.4.17 (core)",
    "@oclif/plugin-search 1.2.16 (core)",
    "@oclif/plugin-update 4.6.13 (core)",
    "@oclif/plugin-version 2.2.16 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.23 (core)",
    "@oclif/plugin-which 3.2.19 (core)",
    "@salesforce/cli 2.68.6 (core)",
    "apex 3.6.3 (core)",
    "api 1.3.2 (core)",
    "auth 3.6.75 (core)",
    "community 3.2.35 (user) published 53 days ago (Sat Oct 12 2024) (latest is 3.3.6)",
    "data 3.11.4 (core)",
    "deploy-retrieve 3.15.13 (core)",
    "info 3.4.21 (core)",
    "lightning-dev 1.9.0 (user) published 54 days ago (Fri Oct 11 2024) (latest is 1.9.4)",
    "limits 3.3.40 (core)",
    "marketplace 1.3.6 (core)",
    "org 5.2.4 (core)",
    "packaging 2.9.3 (core)",
    "schema 3.3.42 (core)",
    "settings 2.4.6 (core)",
    "sobject 1.4.46 (core)",
    "telemetry 3.6.23 (core)",
    "templates 56.3.30 (core)",
    "trust 3.7.43 (core)",
    "user 3.6.3 (core)",
    "@salesforce/sfdx-scanner 4.6.0 (user) published 71 days ago (Tue Sep 24 2024) (latest is 4.7.0)"
  ]
}

[github-actions]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[mdonnalley]

Do you have an expired org that's configured as your default org? If so, you could try removing it as the default org.

Another option is to set JSFORCE_LOG_LEVEL=DEBUG in your environment to see if there's an endpoint that we're retying

[github-actions]

This issue has not received a response in 7 days. It will auto-close in 7 days unless a response is posted.