>
> Running \`exp queue status\` is very slow.
>
> I noticed that after submitting 200 …run jobs the queue, the \`dvc exp queue status\` became very slow.
> In the order of 5 minutes for giving a result.
>
>
>
> dvc doctor:
>
> \`\`\`
> DVC version: 2.36.0 (pip)
> \---------------------------------
> Platform: Python 3.10.8 on Linux-6.0.11-arch1-1-x86\_64-with-glibc2.36
> Subprojects:
> dvc\_data = 0.28.3
> dvc\_objects = 0.14.0
> dvc\_render = 0.0.14
> dvc\_task = 0.1.6
> dvclive = 1.1.0
> scmrepo = 0.1.4
> Supports:
> azure (adlfs = 2022.10.0, knack = 0.10.0, azure-identity = 1.11.0),
> http (aiohttp = 3.8.3, aiohttp-retry = 2.8.3),
> https (aiohttp = 3.8.3, aiohttp-retry = 2.8.3)
> Cache types: hardlink, symlink
> Cache directory: ext4 on /dev/sdb1
> Caches: local
> Remotes: azure, local
> Workspace directory: ext4 on /dev/sdb1
> Repo: dvc, git
> \`\`\`
---
### Author:  [@gregstarr](https://discuss.dvc.org/u/gregstarr)
#### Post date: [February 18, 2023, 3:06pm UTC](https://discuss.dvc.org/t/dvc-exp-show-dvc-queue-status-execution-time/1531/4 "2023-02-18T15:06:20Z")
Is there an older version of DVC which doesn’t have this issue? On a different project I have been using 1.16 or 1.11 (I don’t remember) which seems to be quick. Is there a 2.x version of DVC which doesn’t have the issue?
---
### Author:  [@pmrowla](https://discuss.dvc.org/u/pmrowla)
#### Post date: [February 19, 2023, 2:18am UTC](https://discuss.dvc.org/t/dvc-exp-show-dvc-queue-status-execution-time/1531/5 "2023-02-19T02:18:28Z")
You could use `2.13.0` or earlier, but those releases were prior to `dvc queue` related commands being introduced in DVC. In `2.13.0` and earlier there was a naive implementation for `dvc exp run --queue/--run-all` which would allow you to run multiple experiments, but was not really a functional task queue.
(There is no `dvc queue` command in those releases, so `dvc queue status` and `dvc queue logs` are unavailable)
---
### Author:  [@gregstarr](https://discuss.dvc.org/u/gregstarr)
#### Post date: [February 20, 2023, 6:24pm UTC](https://discuss.dvc.org/t/dvc-exp-show-dvc-queue-status-execution-time/1531/6 "2023-02-20T18:24:33Z")
Okay thanks for the advise. That makes sense because I started seeing the issue when upgrading from 2.9.2 to \>= 2.30
---
### Author:  [@gregstarr](https://discuss.dvc.org/u/gregstarr)
#### Post date: [December 26, 2023, 5:34pm UTC](https://discuss.dvc.org/t/dvc-exp-show-dvc-queue-status-execution-time/1531/7 "2023-12-26T17:34:18Z")
Hello,
I just ran a few experiments and I had to cancel some of them. Now when I run any command relating to experiments, it just sits there and does nothing. This includes `dvc exp show`, `dvc exp list`, `dvc queue status`. I am on v3.33.4.
I was about to post the output of `dvc doctor` but now it seems stuck too.
```auto
(almds) ~/code/almds_prototype[smaller-ecc]$ dvc doctor -vv
2023-12-26 12:31:25,454 DEBUG: v3.33.4 (pip), CPython 3.10.13 on Linux-3.10.0-693.el7.x86_64-x86_64-with-glibc2.17
2023-12-26 12:31:25,454 DEBUG: command: /home/starrgw1/.conda/envs/almds/bin/dvc doctor -vv
2023-12-26 12:31:25,454 TRACE: Namespace(quiet=0, verbose=2, cprofile=False, cprofile_dump=None, yappi=False, yappi_separate_threads=False, viztracer=False, viztracer_depth=None, viztracer_async=False, pdb=False, instrument=False, instrument_open=False, show_stack=False, cd='.', cmd='doctor', func=, parser=DvcParser(prog='dvc', usage=None, description='Data Version Control', formatter_class=, conflict_handler='error', add_help=False))
2023-12-26 12:31:26,011 DEBUG: link type reflink is not available ([Errno 95] no more link types left to try out)
2023-12-26 12:31:26,012 DEBUG: Removing '/home/starrgw1/code/.ksb2t94cSqwG95Rtj4TEeh.tmp'
2023-12-26 12:31:26,012 DEBUG: link type hardlink is not available ([Errno 95] no more link types left to try out)
2023-12-26 12:31:26,012 DEBUG: Removing '/home/starrgw1/code/.ksb2t94cSqwG95Rtj4TEeh.tmp'
2023-12-26 12:31:26,012 DEBUG: Removing '/home/starrgw1/code/.ksb2t94cSqwG95Rtj4TEeh.tmp'
2023-12-26 12:31:26,024 DEBUG: Removing '/scratch/tmp/starrgw1/almds/dvc_cache/files/md5/.6kKKYQ3VnP43w9wAHHKzdg.tmp'
```
and it has been stuck here for 5 minutes or so.
---
### Author:  [@pmrowla](https://discuss.dvc.org/u/pmrowla)
#### Post date: [December 27, 2023, 3:34am UTC](https://discuss.dvc.org/t/dvc-exp-show-dvc-queue-status-execution-time/1531/8 "2023-12-27T03:34:55Z")
It’s hard to tell what the issue might be here. What was the command you used to cancel your experiment runs?
There may still be a hanging DVC or DVC-related Python process left over from the experiments you cancelled, you will probably need to check for this (i.e. with `ps`) and if there are any you may need to force quit them with `kill` or `kill -9` (assuming you were using queued experiments you can also retry doing `dvc queue stop --kill` to forcefully stop any leftover queue processes)
---
### Author:  [@gregstarr](https://discuss.dvc.org/u/gregstarr)
#### Post date: [December 29, 2023, 11:28pm UTC](https://discuss.dvc.org/t/dvc-exp-show-dvc-queue-status-execution-time/1531/9 "2023-12-29T23:28:39Z")
I think this may have been an issue with our cluster or NAS. I will update if the issue returns