Email or username:

Password:

Forgot your password?
Alex Gleason
I'm running into the same performance issues on Ditto that Pleroma has with StatusView. Namely that to render a status we have to get a full account object, 3 stats on the account, and 3 stats on the status. Quotes and reposts add an extra layer of struggle. We can't cache these entities because of the stats, so to cache we have to break them into smaller pieces, cache those, and then recombine in the response. This is exactly what I plan to do.
2 comments
Alex Gleason
I am also thinking about custom database implementations. If I decide to break it into separate pieces again, the choice will be among Nostr relay implementations and not actual databases like Postgres. A relay could use Postgres, but Ditto would want to speak Nostr to it. If that makes sense.
Alex Gleason
Either way, Ditto will need the cache I described in the OP.
Go Up