SupraLabs join request
Hey Ivan!
I saw your TinyDiT-256 model and I am amazed by the results and the image quality of the outputs.
I got your model running instantly on my Kaggle Setup and tried some samples:
Prompts:
PROMPTS = [
"an astronaut riding a brown horse on mars, morning light, dust",
"the Google logo",
"two yellow wooden bricks and a yellow cup of coffee",
"a water bottle standing on the floor",
"a house in the woods",
"a cliff coast, crashing waves in the bottom, breathtaking view",
"a bed room"
]
I wanted to ask you, if you want to join SupraLabs as a new member for pushing our own text-to-image models further.
We did a lot of research before and we never got results like you did ππ
For datasets, we would propose almost the same datasets as you used (it's a funny coindicent because I found your model AFTER I did the dataset research and your GitHub-model-README just instantly proved my decisions π€ππ€© - that's so cool! :D), so:
- ~75% cc1m-cleaned (new source of REAL images and good prompts!)
- ~25% FLUX-Reasoning-6M (same dataset that you used!)
And then a total of e.g. 10M images for ~2-4 epochs.
We are learning a lot from your model setup - and I want to cooperate with you to make a model that is even greater!
At SupraLabs, we soon have 24/7 FREE access to a new server we got from a friend: 2x RTX A6000 48GB (96GB via NVLink), 128GB DDR5 RAM, 4TB NVMe SSD π₯
--> That would be the hardware we'd train the text-to-image model on.
And a question to you: which GPU ("from scratch on one GPU") did you train on?
We'd be happy to work together with you π€
Please tell me if you're interested to be our new member for Computer Vision and Media-Generative AI (t2i, t2v, etc...)!
Thanks, glad the write-up was useful, and nice to see it running on Kaggle! Awesome results!
The GPU was a single RTX PRO 6000 Blackwell (96 GB): 400k steps at batch 256 took 3.5 days at about 0.76 s per step with torch.compile. On two A6000s with DDP you would be roughly in the same range per step, so a 10M-image run for 2 to 4 epochs is realistic on that box.
A few things that mattered more than the dataset list, from the run: - captions: keep a long and a short caption per image and sample between them; long-only hurts short prompts - the timestep shift (2.8 for the 32-channel FLUX.2 latent) and aspect buckets from step one - watch the held-out metrics, not the loss; it barely moves after the first day
On joining: tanks for the invitation, I'm continuing tinydit on my own (RL with Flow-GRPO is next), so I'll stay independent for now, but happy to answer questions here or in the repo issues, and I'd be curious to see what you get with cc1m-cleaned!
Hi there!
Happy to hear that!
It's okay if you wanna keep working alone for now π
We'll OF COURSE include aspect ratio bucketing, long and short captions, etc. π₯π€
We'll stay in contact π
And I am happy to see your future work on TinyDiT π₯
When do you reckong to expect a new version? π π€©
Do you have discord?
My discord: lh_tech_ai
And I am happy to see your future work on TinyDiT π₯
When do you reckong to expect a new version? π π€©
Thanks! I hope in a week or something like this π
Yes, my discord: neoevere
@LH-Tech-AI btw I wrote an article with many details and motivation behind them: https://huggingface.co/blog/ivanmikhnenkov/tinydit-text-to-image-from-scratch-one-gpu
Take a look!
Also, are you on twitter? mine is: https://x.com/ivanmikhnenkov
Sorry, I am not there. I'ma make a friend request on discord.
