You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation runs DBSCAN clustering after every 5 photos, causing performance issues with large photo collections.
Current issues:
- Frequent re-clustering causes unnecessary computational overhead
- No batch processing for multiple uploads
- Potential memory issues with large datasets
- No progress indication during clustering
Impact:
- Poor performance with large photo collections
- High resource usage
- Suboptimal user experience during bulk uploads
Record
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
What happened?
The current implementation runs DBSCAN clustering after every 5 photos, causing performance issues with large photo collections.
Current issues:
- Frequent re-clustering causes unnecessary computational overhead
- No batch processing for multiple uploads
- Potential memory issues with large datasets
- No progress indication during clustering
Impact:
- Poor performance with large photo collections
- High resource usage
- Suboptimal user experience during bulk uploads
Record
The text was updated successfully, but these errors were encountered: