Prior video analytics systems profile the processing pipeline to minimize balance the resource and accuracy trade-off, but they only do it once. Specifically, they exhaustively profiles all configurations on the first x seconds of the video, picks the cheapest configuration that meets a predefined accuracy threshold, and stick with it for the whole duration of the video. However, as we hinted above, if the video content becomes more challenging(e.g. traffic moves faster), using the same configuration will negatively impact the accuracy. On the other hand, same configuration will waste resources if the video content is less challenging(e.g. at a traffic stop).