EVENT processing performance #767

Open
opened 2024-05-18 12:41:38 +12:00 by mikedilger · 0 comments
mikedilger commented 2024-05-18 12:41:38 +12:00 (Migrated from github.com)

The slowest parts (from my recent testing) are where we use serde_json to read/write data types that aren't using speedy (e.g. Person, Relay). This causes event processing to take about 3x as long as it would have otherwise.

We should make new tables for person.metadata and relay.nip11 so that this "structured data" doesn't impede these tables, thus these tables can be fast with speedy.

The slowest parts (from my recent testing) are where we use serde_json to read/write data types that aren't using speedy (e.g. Person, Relay). This causes event processing to take about 3x as long as it would have otherwise. We should make new tables for person.metadata and relay.nip11 so that this "structured data" doesn't impede these tables, thus these tables can be fast with speedy.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nostr/gossip#767
No description provided.