Barry Luijbregts on Nostr: I've been running this for most of the day now, and it seems to be able to keep up. ...
I've been running this for most of the day now, and it seems to be able to keep up. Although I see some lags where it lags a couple of minutes when it needs to process many feeds at once. The bottleneck is the database, which is clear to me. I'll let this run this weekend, so that Azure SQL Database can figure out which queries can benefit from which indexes, and see how the performance profile is after that.
Next is to figure out what the client (app) architecture is going to be.
Published at
2024-08-30 11:46:36Event JSON
{
"id": "9a200a5cb9a2563c0c247b8866dd9d47e6a7a937430941cf13421938a408eef5",
"pubkey": "e3e11bab8bb77d0f26287ef854311adaf5830f2891e1b9d355f55345cfc4a013",
"created_at": 1725018396,
"kind": 1,
"tags": [
[
"proxy",
"https://podcastindex.social/users/podhome/statuses/113050805615261889",
"activitypub"
]
],
"content": "I've been running this for most of the day now, and it seems to be able to keep up. Although I see some lags where it lags a couple of minutes when it needs to process many feeds at once. The bottleneck is the database, which is clear to me. I'll let this run this weekend, so that Azure SQL Database can figure out which queries can benefit from which indexes, and see how the performance profile is after that.\n\nNext is to figure out what the client (app) architecture is going to be.",
"sig": "20ffc266c47a63c8f85e84efd2466a84d00ee6526f28d947415ad0eae325e3d71f495fdb635f46026e5d62860bfec1f9452d38d5da2556f7369e6a11dfa69f35"
}
