Best practices

To minimize disruptions and sunk costs in your labeling jobs, the following are recommended best practices for setting your projects and labelers up for success.

  1. Use Google Chrome. While Labelbox will work on other web browsers, we recommend using Labelbox on Google Chrome to ensure the best experience.

  2. Use one browser window. Using the Labelbox Editor in multiple sessions (i.e., multiple browser windows/tabs or concurrently on multiple machines) is not recommended. For the smoothest experience, make sure you are only using Labelbox in one browser window at a time.

  3. Remember to log out. If you normally use Labelbox on more than one computer, make sure you are logged out of Labelbox on all other computers before logging in on another computer.

  4. Remember that the labeling timer will pause when the Editor is idle for more than 30 seconds. In order to accurately calculate labeling time, Labelbox pauses the timer when a labeler leaves the Editor sitting idle for 30 seconds or more. If a user clicks on an Attachment link that takes them out of the Editor, the timer will pause if no movement is recorded after 30 seconds. Actions like zooming, clicking, or moving the cursor will resume the timer.

  5. Optimize asset size. The most effective way to optimize Editor performance is to limit asset size to the maximum resolution needed for accurate labeling and effective model training. Some training tasks may require more resolution than others, but generally, we recommend images no larger than 4000x4000px and videos with frame rates no greater than 30fps.

  6. Delegate access to your data storage. For optimal security and performance, use IAM delegated access to connect your data into Labelbox. This will allow you to keep your assets in cloud storage and simply delegate Labelbox the limited access it needs to display your assets in the Editor efficiently.

  7. Set up a CDN. If your labelers are accessing your assets from many different locations, or are located in a different timezone from where your data is stored, setting up a CDN can speed up delivery of assets to your labelers.

  8. Conduct a trial run. Prior to kicking off a labeling project, set up a test project with your assets to be labeled, and simulate the environment you expect your labelers to be in when labeling. Namely, test during the peak hours you expect labelers to be working on your job, from the area they will be located, and on the network and machines they will be using to access Labelbox. This will give you an opportunity to identify and reduce/resolve any latencies or issues upfront, rather than during an ongoing labeling job.


Did this page help you?