Looks at potential to me, what are you looking at? You should update Kohya to 22.3 though
Looks at potential to me, what are you looking at? You should update Kohya to 22.3 though
DOh, i see, yeah, let me do it as well. potential, means, when i run training, it doesnt take load on gpu it should take....usually, when the temperature gets higher, when the gpu is totally using it's power, but when i run training, with kohya, it only gets half of the temperature, compared to it usually takes.
Bsince today there's 22.4
Loohhhh 
What changes?
What changes?DOh, i can just edit the bat file and add autoupdate, it should update automatically, everytime it runs?
BGitHub
2023/12/28 (v22.4.0)
Fixed to work tools/convert_diffusers20_original_sd.py. Thanks to Disty0! PR #1016
The issues in multi-GPU training are fixed. Thanks to Isotr0py! PR #989 and #1000
--ddp_gr...
Fixed to work tools/convert_diffusers20_original_sd.py. Thanks to Disty0! PR #1016
The issues in multi-GPU training are fixed. Thanks to Isotr0py! PR #989 and #1000
--ddp_gr...
LOhhh seems useless unless you're running more than one GPU
BPagedAdamW added as optimizer and for the rest mostly fixes, but also some new options for sampling
LOk now im interested, whats pagedadamw
Lok yeah im about to do a training it looks interesting
LWWhat's the command to update Kohya again I forgot?
Lnevermind just a git pull
LLet's hope nothing is broken now
LIt broke blip ughhhh
LThe only thing that broke, it seems, was Blip captioning, but as I recall, I was using some type of rollback version of something. I think it was transformers. Honestly most of these captions tools are lousy and if you are using a smaller data-set manual captioning is best
Mdoes this mean we can do BF16 training now?
RCan I train a lora model for sdxl-turbo?
Fyes not but i still put if someone tries or uses
Fwhat is your it / s ?
Fhello. are you installing on activated venv?
Fwhich app_
Fyes i am doing that all the time. uses around 17 gb
Ftrue please download attachments. they got updated
Ftrue now in those zips
Fno it is not an issue. also you can upgrade kohya to latest
Fit is not currently at you
Fsadly not . it is gpu type limitation
Fi dont know yet sadly
Mthank you to use both gpus should we add "-ddp_gradient_as_bucket_view" to additional parameters?
MThe issues in multi-GPU training are fixed. Thanks to Isotr0py! PR #989 and #1000
--ddp_gradient_as_bucket_view and --ddp_bucket_viewoptions are added to sdxl_train.py. Please specify these options for multi-GPU training.
--ddp_gradient_as_bucket_view and --ddp_bucket_viewoptions are added to sdxl_train.py. Please specify these options for multi-GPU training.
Mhow do we specify these options in kohya?
Fyes i think
Fextra parameters
XCan I do multi-gpu training in Koyha if the graphics cards are different models/different Vram? (example, RTX 3080 and RTX 3090). Sorry to ask before testing, it's that I need a new power supply if I want to use both cards.
Ait is around 2s/it, a 3090ti has 1.12s/it on the same settings
Athe only time when the 4090 is faster, is if i increase the batch size to 4, its around 30% faster than the 3090ti then. But its still a bit weird
LDoes anyone know the Syntax for the regional prompter well. I'm getting better with prompts but if I have two Character Loras what's the best way to set up the prompt?
![Digital [Starburst]](https://cdn.discordapp.com/avatars/220961909447458817/8ecbbb3132fc6e44312f3d6d2ae3df69.webp?size=40)
DI'm getting [virtualMemoryBuffer.cpp::nvinfer1::StdVirtualMemoryBufferImpl::resizePhysical::140] Error Code 2: OutofMemory when attempting to generate the TensorRT Default Engine
DIt also says the Engine is invalid and I need to verify the engine was built correctly
DI'm using your automated installers from Patreon and am in Development mode until the install is complete and then switch back to Master.
DI checked my CUDA install and it is set to use version 11.8 which I assume is correct.
DI have 12.3 installed, but it is not set in Path except that CUDA_PATH_V12_3 is set to that version. I installed 12.3 because it was the only way to check the samples with Visual Studio 2022.
DOnce I tested it, and it worked I changed the environment variables to 11.8.
DUpdating torch, torchvision, and xformers tossed another error saying torch could not access the GPU. It said I can set a flag, so it won't run the check, but I don't want to do that.
DI am just rerunning your install program to fix it.
DYour install program reinstalled cu118, so I'm assuming it must be that version which means I'm running the correct version of CUDA, so I don't think TensorRT is working at the moment.
DSo it is saying UNSUPPORTED_STATESkipping tactic...insufficient memory. Is there a launch setting such as --medvram I need to use? I haven't tried that yet, but that's next.
DIt would make sense. The error keeps stating [virtualMemoryBuffer.cpp...etc
DYeah I think that's the issue. The message ends with OUT_OF_MEMORY (No further information). It has to be running out of VRAM.
DIt is telling me what the problem is, but I'm not seeing it for some reason. Reading the error generated more carefully made it clear, but I'm not sure what to do about it. I set the launcher to --lowvram even though I have 12GB of it, but that still may not be enough. You recommended we choose a machine with at least 24GB of VRAM on RunPod if we are using it.
DI was following your tutorial for Kohya, but if I can't even load Tensor then I highly doubt I can run that. The tutorial mentions it can be run on 12GB of VRAM, but I probably won't struggle with it to get it to work.
