/jobs/:id is MUCH slower than /jobs about codem-transcode HOT 5 CLOSED

How many jobs are in your database, and which database are you using (sqlite, mysql?)?

/jobs simply returns the active jobs from memory, while /jobs/:id performs a trip to the database to retrieve that job. If there are a lot of jobs in your database that might be the reason (especially if you're on sqlite), or the machine is so CPU-bound that reading the database becomes slow. Try purging old finished jobs (there's an endpoint for that).

from codem-transcode.

Also, I just pushed a commit (9e75228) that returns a job from memory if it exists. There's no need to go to the database if the job is already in memory.

from codem-transcode.

OH, of course! I totally forgot about sqlite... I was using it to test before. Thanks a lot @tieleman!

from codem-transcode.

np, good luck!

from codem-transcode.

Just to let you know: I applied 9e75228 and it by itself already solved the problem. Sure, I still have to use a decent database, but now I'm able to procrastinate a bit more on that on focus on other things. hehe

Thanks again @tieleman!

from codem-transcode.