Skip to content
This repository has been archived by the owner on Sep 18, 2024. It is now read-only.

NNI v3.0 - NAS search doesn't start at all #5694

Open
chachus opened this issue Oct 10, 2023 · 5 comments
Open

NNI v3.0 - NAS search doesn't start at all #5694

chachus opened this issue Oct 10, 2023 · 5 comments

Comments

@chachus
Copy link

chachus commented Oct 10, 2023

Describe the issue:
Using version 3.0, the tutorial HelloNAS doesn't work at all. Once the experiment is launched an error is raised regarding the HTTP connection with the rest server. Also there is a problem with the gpu info collection process, which is spawned multiple times slowing down the pc.

Environment:

  • NNI version: 3.0
  • Training service (local|remote|pai|aml|etc): local
  • Client OS: Ubuntu
  • Server OS (for remote mode only):
  • Python version: 3.9
  • PyTorch/TensorFlow version: 1.12
  • Is conda/virtualenv/venv used?: yes
  • Is running in Docker?:

Configuration:

  • Experiment config (remember to remove secrets!):
  • Search space:

Log message:

How to reproduce it?:
Run the HelloNAS tutorial using NNIv3.0

@6liuyu123
Copy link

I have some issue about http connect whether use Linux or Windows

@chachus
Copy link
Author

chachus commented Oct 10, 2023

Same thing

@will-leeson
Copy link

I am experiencing the same issue

@keyboardwarrior1110
Copy link

Hello,

I believe the connection issue might be due to the ports not being opened, causing the firewall to block the connection. You can open a port by going to Windows Defender and adjusting the advanced settings. For more detailed instructions, you might want to search online. I hope this helps.

Additionally, I've also tried to utilize the GPU to test my NAS, but it resulted in the computer running a heavy load of programs, leading to a crash, lol.

@chachus
Copy link
Author

chachus commented Jan 31, 2024

Additionally, I've also tried to utilize the GPU to test my NAS, but it resulted in the computer running a heavy load of programs, leading to a crash, lol.

That is the main damn problem, and seems still unresolved to this date.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants