Skip to content

About FLOPs and running time #11

@ChimpOnCloud

Description

@ChimpOnCloud

Great work,
I tested your code on DiT-XL-2-256x256,
with command

python sample.py --image-size 256 --num-sampling-steps 250 --cache-type attention --fresh-threshold 4 --fresh-ratio 0.07 --ratio-scheduler ToCa-ddpm250  --force-fres
h global --soft-fresh-weight 0.25 --seed 1234 --test-FLOPs

It shows 43.420574210048 TFLOPs Total Sampling took 9.7924873046875 seconds

with command

python sample.py --image-size 256 --num-sampling-steps 250 --cache-type attention --fresh-threshold 1 --fresh-ratio 0.07 --ratio-scheduler ToCa-ddpm250  --force-fres
h global --soft-fresh-weight 0.25 --seed 1234 --test-FLOPs

It shows 103.549585270784 TFLOPs Total Sampling took 10.506012695312501 seconds

So the FLOPs were cut to nearly half but running time seems not changed apparently. What is the probable reason of this phenomenon?

I ran the above code on a single NVIDIA 3090 RTX.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions