Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI becomes slow after 300-400 annotations #39

Closed
wronk opened this issue Aug 27, 2018 · 6 comments
Closed

UI becomes slow after 300-400 annotations #39

wronk opened this issue Aug 27, 2018 · 6 comments
Assignees
Labels
bug Something isn't working enhancement New feature or request
Milestone

Comments

@wronk
Copy link

wronk commented Aug 27, 2018

I'm labeling large satellite images with hundreds to a few thousand objects of interest.

I noticed that after about 300-400 annotations, the UI slows down. It might take the program ~1 sec to become responsive again after creating a new bbox. After about 800-1000 annotations, it's nearly unusable -- adding an annotation might require ~5 seconds before it will register. For now, I'm just cropping my large images into smaller pieces as a workaround, but it'd be a lot nicer to add all annotations to a single large image (as raw satellite imagery often comes in fairly long strips). I'm using a 2017 MacBook pro to do the labeling.

I don't know enough about the backend to suggest a fix, but happy to answer questions if it's helpful.

@nmanovic nmanovic added bug Something isn't working enhancement New feature or request labels Aug 27, 2018
@nmanovic
Copy link
Contributor

@wronk ,

We will look at the problem. If you can provide us your image + annotation file it will help us to reproduce it easily on our side. Probably our tool isn't optimized for such cases. Need to check how to improve it.

@nmanovic
Copy link
Contributor

Also I remember that we had similar problems for semantic/instance segmentation and Boris fixed similar issues. If it is the case the problem will be fixed with next major release.

@wronk
Copy link
Author

wronk commented Aug 28, 2018

@nmanovic, thanks for checking into this. Here are both files -- let me know if you have any problems or need more help.

CVAT_issue_39_example_case.zip

@nmanovic nmanovic added this to the Release 0.2.0 milestone Sep 20, 2018
@nmanovic
Copy link
Contributor

@bsekachev ,

Could you please look at the problem? Was it fixed already?

@nmanovic
Copy link
Contributor

Hi @wronk,

  • I can reproduce your performance problems on the latest version of CVAT.
  • I cannot upload your annotation file as is because a lot of coordinates for bounding boxes are out of image size. My guess that huge image resolution can be a reason for that. Did you crop the attached image or it has original size?

We will work to resolve both problems. Thanks for your feedback.

@wronk
Copy link
Author

wronk commented Sep 25, 2018

Hey @nmanovic, I think I've gotten this working. I do have 2 versions of the image, but I think I have the correct one included here. I was able to remake the task with the included files.

I did have an issue where I had to manually change the version tags in the annotation file to get it to sync properly to a newly created task. Specifically, these lines in the xml file need to match the task you create (e.g., task 25) on your cvat instance:

  <meta>
    <task>
      <id>25</id>
        <segment> 
         <id>25</id>
          <start>25</start>
          <stop>25</stop>
          <url>http://localhost:8080/?id=25</url>
        </segment>

Let me know if that fixes it for you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants