Polygon Segmentation Loading Time

[vchaparro]

Describe the bug
After Labeling Brush and Polygon, the loading time in tasks is huge, could take upto minutes sometimes.

To Reproduce
Steps to reproduce the behavior:

1. Label an image with Polygon or Brush segmentation, submit
2. Go to Tasks and try to load the image
3. You will observe that it takes a huge time to load (2-3 minutes sometimes)

Expected behavior
Should Load quickly

Environment (please complete the following information):Environment (please complete the following information):

• OS: Ubuntu
• Label Studio Version 1.7.2

Additional context
According to the issue #476, it should be fixed with version 1.3.0 release, however, I'm getting the same behaviour using version 1.7.2. I am using images of approximately 1500x1500 (around 5 MB) with segmentation polygons. When attempting to open these pre-labeled images, which have a relatively high number of polygons per image (it's about buildings footprint segmentation), it takes too long to open. Additionally, the user experience suffers when transitioning from one image to the next, zooming, and so on. The client-side web browser begins to consume high CPU resources.

[makseq]

Is it possible to open the browser console and record a video with this problem?

[vchaparro]

Hi,
Sure

Thanks in advance!

kazam_8bmku52o.mp4

[vchaparro]

Hi @makseq ,

Did you have the chance to watch the video? By the way, I've noticed it works on Chrome, but not on Firefox, just in case you use Firefox.
Thanks!

[mnaranjorion]

Good morning,

Do you have an update on this issue? I find myself in the same situation, as when I try to upload images with multiple tags, the upload time takes a long time and even crashes.

The only solution I can think of is to split the image to reduce the number of annotations, but that would lose the reference and make annotation very difficult.

Best regards.

[makseq]

@vchaparro I've checked your video. Seems you have large amount of regions, so your browser has this performance problems. I am not sure that a simple solution exists here, I will discuss it with our frontend team.

Also it would be helpful if you could check the Network console too, how big is the payload for api/tasks/<id> calls there?

[vchaparro]

Hi @makseq, find attached a file with the payload of one of these tasks.
payload.txt