Unable to share files on Private Chat #1

Open
opened 2026-03-10 16:39:46 +00:00 by fabby · 2 comments
Owner

When I open a private chat in Butter, I can send messages and run polls, but I am unable to send images or videos.
On the sender's side I see the file in the chat with a "Retry" label at the top.
On the receiver's side, I see an empty message.

When I open a private chat in Butter, I can send messages and run polls, but I am unable to send images or videos. On the sender's side I see the file in the chat with a "Retry" label at the top. On the receiver's side, I see an empty message.
Owner

I think this is related to what I've been seeing. I don't think it is anything specific to private chat / DMs. It is just that sqlite is very slow and the db is getting locked.

We need to tune sqlite somehow OR move to postgres.

I think this is related to what I've been seeing. I don't think it is anything specific to private chat / DMs. It is just that sqlite is very slow and the db is getting locked. We need to tune sqlite somehow OR move to postgres.
Owner

https://element-hq.github.io/dendrite/installation/planning

Dendrite can run with either a PostgreSQL or a SQLite backend. There are considerable tradeoffs to consider:

PostgreSQL: Needs to run separately to Dendrite, needs to be installed and configured separately and will use more resources over all, but will be considerably faster than SQLite. PostgreSQL has much better write concurrency which will allow Dendrite to process more tasks in parallel. This will be necessary for federated deployments to perform adequately.

SQLite: Built into Dendrite, therefore no separate database engine is necessary and is quite a bit easier to set up, but will be much slower than PostgreSQL in most cases. SQLite only allows a single writer on a database at a given time, which will significantly restrict Dendrite’s ability to process multiple tasks in parallel.

https://element-hq.github.io/dendrite/installation/planning Dendrite can run with either a PostgreSQL or a SQLite backend. There are considerable tradeoffs to consider: PostgreSQL: Needs to run separately to Dendrite, needs to be installed and configured separately and will use more resources over all, but will be considerably faster than SQLite. PostgreSQL has much better write concurrency which will allow Dendrite to process more tasks in parallel. This will be necessary for federated deployments to perform adequately. SQLite: Built into Dendrite, therefore no separate database engine is necessary and is quite a bit easier to set up, but will be much slower than PostgreSQL in most cases. SQLite only allows a single writer on a database at a given time, which will significantly restrict Dendrite’s ability to process multiple tasks in parallel.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
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: butter/keanu-weblite#1
No description provided.