Google Diet Colab Notebook

[ixfd64]

Originally Posted by SimonVall00

I have succesfully run mfaktc in Google Colaboratory. I have created a Github repository with the Notebook i used.



Here is a link to the repository.
https://github.com/SimonVall00/mfaktc-google-colab

This link is giving a 404 error. Is there an alternative repository?

[9vLYvxWUJ7Dy2Hb]

Originally Posted by ixfd64

This link is giving a 404 error. Is there an alternative repository?

Not sure if you found your answer in the meantime. Since it took some to find it when I started here's a reference for those reading only the last page of the thread:


The generation of the Notebook including access keys is integrated into GPU72 now.
https://www.gpu72.com/
You can create an account there and generate a notebook via the menu Notebook access Keys. Maybe a mod can put this info onto the first page of the thread?

[Uncwilly]

I am getting about 30 min to 1 hour sessions of CPU only sessions using the GPU72 notebook. The problems that were happing before with the payload fetch have cleared. And I have been getting about 30 min to 1 hour of GPU in a single session once every 24 hours.

[lycorn]

I use 5 google accounts and am able to run simultaneously12 notebooks on them (CPU only sessions, which always last 12 hours each) and every day I run a 10-hour long GPU session, normally T4s. I only run ECM on the CPUs and TF on GPUs
I am not using GPU72, though.

[chalsall]

Originally Posted by Uncwilly

I am getting about 30 min to 1 hour sessions of CPU only sessions using the GPU72 notebook. The problems that were happing before with the payload fetch have cleared. And I have been getting about 30 min to 1 hour of GPU in a single session once every 24 hours.

Yup. Fixed the profoundly stupid SPE wrt Colab P-1 assignments.

And, I also have been getting between 30 to 90 minutes of GPU access per account per day for the last couple of weeks. CPU-only is also regularly available, but they only last between 30 minutes to two hours.

Four of my thirteen accounts are being presented with a new message every time I launch an instance. Something along the lines of "Colab is for interactive usage. Are you still there?" with a "Cancel" button which must be clicked with a mouse (hitting return doesn't work).

[lycorn]

I got it too, once or twice in the last two weeks.

[Uncwilly]

Chris, can you upgrade your copy of mprime for the notebooks to the latest release? There have been some significant improvements that will speed P-1.

[petrw1]

I first got GPUOwl running on Colab on Sept 19, 2020.
About 10 days later I started a second instance.
I have been attempting to get 2 P100 instances per day since.
Almost every day I get 2 and they last an average of about 8 hours each; over 200 GhzDays.

In any case in these 165 days my Colab sessions GhzDays (29,300) have now surpassed my 4 core i5-3570K which started Oct 1, 2017; 1249 days ...yes almost a 3 year head start.