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

is kolia support python3.6? #23

Open
Yuruzu opened this issue Jan 15, 2022 · 5 comments
Open

is kolia support python3.6? #23

Yuruzu opened this issue Jan 15, 2022 · 5 comments

Comments

@Yuruzu
Copy link

Yuruzu commented Jan 15, 2022

No description provided.

@rentruewang
Copy link
Owner

rentruewang commented Jan 15, 2022

Sorry, not yet. It doesn't even support python3.7 (#7) haha. We'll get there eventually 😊

@Yuruzu
Copy link
Author

Yuruzu commented Jan 16, 2022

SO SAD

@Yuruzu Yuruzu closed this as completed Jan 17, 2022
@Yuruzu Yuruzu reopened this Jan 17, 2022
@Yuruzu
Copy link
Author

Yuruzu commented Jan 17, 2022

Sorry, not yet. It doesn't even support python3.7 (#7) haha. We'll get there eventually 😊

hi, i try to use kolia in python3.8, but i miss trouble too. i follow the getting-started.py and use dgl package to train graph data, but i have the same RuntimeError: CUDA out of memory., can u give a more detailed example of dividing the training, validation, test data set? i should add the code (lazy_input, lazy_label) = lazy(input, label, batch=0) before or after dividing the dataset ? thanks a lot!

@rentruewang
Copy link
Owner

Hi, thanks for the report!

Koila is a gradient accumulator, so what happens is that is automatically tries to split up the batches (in the background) in the case that there is OOM. However, it doesn't know how to handle "some" layers currently, so it has no effect on those layers. This is done silently in the background. Turns out that if a layer is not recognized by the framework, it doesn't prevent OOM.

As of right now, this project is in a re-write (see #18), which should've happened last month. But I just got a job at a company so currently the schedule is very messy. So I have to apologize for not having time to fix many existing bugs, which would be automatically fixed in a more modular design.

Thanks for reading!

@Yuruzu
Copy link
Author

Yuruzu commented Jan 25, 2022

It's okay, looking forward to the next version

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

2 participants