brian-doherty

I will have a look but probably not this week as I have a business trip.

I"m using https://feeds.simplecast.com/JGE3yC0V On Fri, Jul 28, 2023 at 6:30 AM tamland ***@***.***> wrote: > I'm unable to reproduce the width issue. Maybe we aren't using the same > feed...

OK. The backend is a gonic server. LMK if you want me to take some logs of some sort.

Could it be a cache miss and then a delay from last.fm? I guess probably not if it happens to manifest for the guy with 3M tracks but I thought...

Scan or not, when you run this query you're potentially asking for a very large number of rows very frequently, even though you're keeping the info cached for 30 days....

My bad. Maybe you need an index on updated_at? Then it can go straight to the record with the lowest value instead of searching for one that's below.

What if you order by updated_at, instead of id? Then it doesn't have to search at all?

You could also structure it as two queries -- do an empty one if its there, otherwise do the oldest if it's old enough. On Tue, Mar 5, 2024, 5:14 ...

Now those are queries I'd expect to be slow. :D Start caching the sums and counts in the DB?

Yeah this allows snaps to start, but you're right that the snap doesn't pick up the nsdo mount ns. Have not solved that one. It will for example screw up...