cluster is very slow
Closed this issue · 11 comments
Hi, I try to reproduce the model on market dataset, all the settings are default.
I found the cluster time is very long, ~300s on cpu and 600s on gpu.
The os is linux, and my card is RTX 3090.
Is there any suggestions to improve the cluster?
We conduct the clustering every 2 epochs, thus 300s once means 5h for 120epoch. I think it is ok. Sometimes the data IO also affects the times. If you want to accelerate it, you can try to use multithreading to conduct the image clustering in parallel.
We conduct the clustering every 2 epochs, thus 300s once means 5h for 120epoch. I think it is ok. Sometimes the data IO also affects the times. If you want to accelerate it, you can try to use multithreading to conduct the image clustering in parallel.
Thanks your reply. I had tried to paralle the cluster step by multiprocessing. However,the code was stuck in
Shoud I replace multiprocessing with multihereading? I think maybe the multi threads in faiss conflicts with current multiprocessing.
I donot know, but you can try to turn off the faiss parallelism (if used), because most time is cost on repeated clustering for every ID rather than clustering once.
Yes, the visualization on holistic dataset is much better, especially on DukeMTMC-reID. You can also adjust the hyper-parameters on line 193, 194 in trainer.py to obtain better visualization.
Since the clustering effect of human body parts on the occlusion dataset is not very good, what is the reason for the high reid accuracy?
As can be seen from the above pictures, only a small part of the human body has been noticed, which means that the local features seem to play a relatively limited role, but the head area seems to be activated.
Sorry, but we have not compared the learned semantic and extra semantic on occluded datasets. Maybe on the occluded dataset, only focusing on the most important parts (or always visiable parts) is enough.
Thank you. I will try to compare them to validate it.