[QUOTE=xx005fs;528372]Any GPUOWL executable compiled on linux using rocm/nvidia driver (the latter I haven't tested) works just fine with colab. Since I personally had a linux system with rocm, compilation was as simple as invoking make in the terminal. I just simply popped the executable and a worktodo.txt file in the google drive, created a folder for all of them, and then it's crunching happily on those nvidia gpus.

I am having a lot of trouble finding cudalucas linux executables, neither could i find the source code. It will be great if I test the speed of cudalucas on those K80s to compare with gpuowl performance.[/QUOTE]

Here is CUDALucas posted by Dylan14
[url]https://mersenneforum.org/showpost.php?p=527191&postcount=178[/url]

It works fine on Google Colab.

But on Kaggle it is complaining about:
/lib/x86_64-linux-gpu/libm.so.6: version 'GLIBC_2.27' not found

How did people get CUDALucas to work on Kaggle?

[QUOTE=ATH;528378]But on Kaggle it is complaining about:
/lib/x86_64-linux-gpu/libm.so.6: version 'GLIBC_2.27' not found[/QUOTE]

Probably related... When I first tested my reverse tunnel on Kaggle it didn't work. The SSHd executable I compiled on Colab complained about the same error when running on Kaggle.

I've found that some executables compiled on Colab don't work on Kaggle, but conversely those compiled on Kaggle work in both environments.

ok, I got CUDALucas compiled on Kaggle, it was actually pretty easy. I usually want to avoid compiling at all cost, because I'm bad at Linux.


EDIT:

Managed to upload the wrong file I think, this is the correct one:
[URL="http://hoegge.dk/mersenne/kaggle/cudalucas.tar.gz"]cudalucas.tar.gz[/URL]

[QUOTE=Dylan14;528193]After a bit of trial and error (plus some work in automating the checking of the logs for errors), I have a script that can be used to compile and run Mlucas, without needing to tunnel in. The script is below:

[CODE]#code to compile and run Ernst Mayer's mlucas
import os
from google.colab import drive
if not os.path.exists('/content/drive/My Drive'):
drive.mount('/content/drive')

!apt-get install gcc-8
%cd 'content/drive/My Drive/'
if not os.path.exists('/content/drive/My Drive/mlucas/'):
!mkdir [B]mprime[/B]
...

[/CODE][/QUOTE]Well done. But I think that mkdir would be [B]mlucas[/B]

[QUOTE=Fan Ming;528367]I succeeded at compiling gpuowl on Colab after soving many compilation errors.
Attached is the compiled executable.
Steps for using this executable on Google Colab(Ignore if you already know):
1.Create a folder on Google drive named "gpuowl-master".
2.Upload attached executable "gpuowl.exe" in this folder.
3.Use this ipynb code(don't forget to turn GPU accelerate on):
[CODE]import os.path
from google.colab import drive

if not os.path.exists('/content/drive/My Drive'):
drive.mount('/content/drive')

%cd '/content/drive/My Drive/gpuowl-master/'

!cp 'gpuowl.exe' /usr/local/bin/
!chmod 755 '/usr/local/bin/gpuowl.exe'

!/usr/local/bin/gpuowl.exe -use ORIG_X2[/CODE]

It seems work well, here is the output information(manually stopped after I see it seems work well):
[CODE]/content/drive/My Drive/gpuowl-master
2019-10-19 16:31:38 gpuowl
2019-10-19 16:31:38 Note: no config.txt file found
2019-10-19 16:31:38 config: -use ORIG_X2
2019-10-19 16:31:38 77936867 FFT 4608K: Width 256x4, Height 64x4, Middle 9; 16.52 bits/word
2019-10-19 16:31:38 OpenCL args "-DEXP=77936867u -DWIDTH=1024u -DSMALL_HEIGHT=256u -DMIDDLE=9u -DWEIGHT_STEP=0x1.65cdc45f71f4cp+0 -DIWEIGHT_STEP=0x1.6e52dd530031p-1 -DWEIGHT_BIGSTEP=0x1.306fe0a31b715p+0 -DIWEIGHT_BIGSTEP=0x1.ae89f995ad3adp-1 -DORIG_X2=1 -I. -cl-fast-relaxed-math -cl-std=CL2.0"
2019-10-19 16:31:40

2019-10-19 16:31:40 OpenCL compilation in 1453 ms
2019-10-19 16:31:50 77936867 OK 1000 0.00%; 3929 us/sq; ETA 3d 13:04; 9711fce020e74461 (check 2.15s)
2019-10-19 16:32:39 Stopping, please wait..
2019-10-19 16:32:41 77936867 OK 13500 0.02%; 3961 us/sq; ETA 3d 13:44; 350e9c68bedf46b6 (check 2.18s)
2019-10-19 16:32:41 Exiting because "stop requested"
2019-10-19 16:32:41 Bye[/CODE][/QUOTE]

So why my attachment disappeared without notification... Did it violate any rules? Here I reupload it in zip.

[QUOTE=kriesel;528386]Well done. But I think that mkdir would be [B]mlucas[/B][/QUOTE]


Yep, that was a SPE as I must have just copied that over from the mprime script. Fixed.

[QUOTE=ATH;528378]Here is CUDALucas posted by Dylan14
[url]https://mersenneforum.org/showpost.php?p=527191&postcount=178[/url]

It works fine on Google Colab.

But on Kaggle it is complaining about:
/lib/x86_64-linux-gpu/libm.so.6: version 'GLIBC_2.27' not found

How did people get CUDALucas to work on Kaggle?[/QUOTE]

I had to import a custom repository to install gcc8 and all the other updates to make softwares run on kaggle as it's running gcc6, especially gpuowl when it will frequently complain about missing libraries.

If you are considering running CUDALucas on kaggle, might as well run gpuowl since on the P100 GPU, gpuowl is around 1170us/it, while on CUDALucas (if i remembered correctly from my GCP instances back then) was around 1800us/it. Although robust error checking isn't required for these server parts with ECC, it's definitely recommended in my eyes still.

[QUOTE=Fan Ming;528390]So why my attachment disappeared without notification... Did it violate any rules? Here I reupload it in zip.[/QUOTE]

Nice! I'm curious though about the changes you made - perhaps you could submit a pull request at github to add to the code?

On another note, using Google Drive in Colab, it prompts me basically every time for the "verification" code that you get from your email... is there a way around that so I only have to do that once? Or maybe I'm doing something wrong here...

[QUOTE=Fan Ming;528390]So why my attachment disappeared without notification... Did it violate any rules? Here I reupload it in zip.[/QUOTE]That was my oops (I believe). While .exe is an acceptable attachment type, it is too easy for someone to put something untoward up and having as an .exe could allow a user to accidentally run it. Zip's are better, since the user has an extra step of interaction. I dl'ed your attachment, ran a virus check on it zipped it, then went in and was swapping the zip in. (You have a low post count, so I was being cautious.) I was putting a note on the post. Then I decided to leave it be and closed the window and left for a funeral (extended family). I did not realize the deleted attachment would 'take' that way. :redface:

Sorry.

[QUOTE=kracker;528397]Nice! I'm curious though about the changes you made - perhaps you could submit a pull request at github to add to the code?[/QUOTE]
I just initized git ([B]!git init[/B]) and installed libgmp3-dev([B]!apt-get install libgmp3-dev[/B]), and then I changed all [B]<filesystem>[/B] to [B]<experimental/filesystem>[/B], [B]fs = std::filesystem[/B] to [B]fs = std::experimental::filesystem[/B] in .h and .cpp files which contains them. All this changes are learned from Google, and the changes in source files are just
compatible for older gcc versions(I saw the gcc version for notebooks on colab are 7.x when installing libgmp3-dev. When I googled the missing <filesystem> error later, I realized this and the way to solve the error I googled is exactly OK).

[QUOTE=kracker;528397]On another note, using Google Drive in Colab, it prompts me basically every time for the "verification" code that you get from your email... is there a way around that so I only have to do that once? Or maybe I'm doing something wrong here...[/QUOTE]
Every time I log in my newly-registered Google account I have to sent a pin code to my smartphone.. But this because I'm from China, where cannot access Google unless using proxy from other country.. So maybe Google thought that my behavior is suspect. However, my older Google account doesn't have this problem and can login directly. No idea about why...

[QUOTE=Uncwilly;528401]That was my oops (I believe). While .exe is an acceptable attachment type, it is too easy for someone to put something untoward up and having as an .exe could allow a user to accidentally run it. Zip's are better, since the user has an extra step of interaction. I dl'ed your attachment, ran a virus check on it zipped it, then went in and was swapping the zip in. (You have a low post count, so I was being cautious.) I was putting a note on the post. Then I decided to leave it be and closed the window and left for a funeral (extended family). I did not realize the deleted attachment would 'take' that way. :redface:

Sorry.[/QUOTE]

That's OK:smile:. I got it.