Not sure, but i think yesterday also was zero on graph. Now there 2724 and 2017. Some bag with graph. Day did not ended, stat for this day not calculated yet, but graph try display this day.
It’s an ongoing problem we are currently dealing with. The service works, but is unfortunately heavily rate limited.
We had one server going down, taking all the data on the server with it. All of that was replicated, so nothing was lost, but the service is running on tight budget, given that it’s free and one server out will cause things to overload.
I think that was about money not solving the previous performance issue, because adding another server would not have helped, the application needed (or probably still needs) refactoring.
I think AcoustID now in read-only mode. API return OK for submissions, so maybe they store in some buffer storage until better times. Maybe not. There is few looks-like-performance-related commits in git log
Do notice the git log dates fit with this thread. I assume the dev is currently hitting the AcoustID server with a tuning fork until he can get it back into singing the correct tune.
I think it is a problem if, when submitting Fingerprints via Picard, Picard reports that the Fingerprint was successfully submitted to AcoustID, when in fact it was not. Having said that, I’m not sure at which end the problem lies.
Submissions are processed asynchronously by a background job. However, this normally only takes a few seconds… API documentation
As far as i understand normal AcoustID API behavior is put submission to database or some buffer and return status 200 (Ok) to client. Seems like this part of AcoustID work well all the time. But another part, that shall somehow process submission and make it usable for users not work at lest last 9 days
That looks promising. Acoustids that I submitted a week ago haven’t yet appeared on the recordings; I imagine there is a very large backlog and it may take some days to catch up.