Cannot connect to a high RAM runtime even with 544 compute units

[RobinGanesan]

Expected Behavior

should be able to connect to high RAM runtime

Current Behavior

Will not connect me to a high RAM runtime; the same thing is happening for someone else in our lab with a Colab "pay as you go" subscription. We have successfully used Colabfold a few weeks ago.

However, I went into "making the most of your Colab subscription and ran the same code and got connected to a high RAM runtime

Steps to Reproduce (for bugs)

Please make sure to reproduce the issue after a "Factory Reset" in Colab. If running locally ypdate you local installation colabfold_batch to the newest version. Please provide your input if you can share it.

ColabFold Output (for bugs)

Please make sure to also post the complete ColabFold output. You can use gist.github.com for large output.

Context

Providing context helps us come up with a solution and improve our documentation for the future. I'm running the notebook in this link https://colab.research.google.com/github/sokrypton/ColabFold/blob/main/AlphaFold2.ipynb#scrollTo=mbaIO9pWjaN0

Your Environment

Include as many relevant details about the environment you experienced the bug in.

• Git commit used
• If you run it on a local system. Please add the server specifications not being run on a local system
• Operating system and version: Windows 10 pro version 22H2, 64 bit

[sokrypton]

This appears to be a google colab issue... The new default is high-memory and A100 GPU (currently in high demand and unavailable). To fix this issue, you'd need to downgrade the GPU from A100->V100->T4.

I've updated the notebook to force the default to be low-mem and T4.

[RobinGanesan]

Thanks, Sergei. Unfortunately, this setting does not allow me to complete my structure prediction. What else can I do?

[sokrypton]

Try increase to high-memory but keep GPU at V100 or T4