-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Take abou half minute doing hundries "peewee: ('SELECT "t1"."id", "t1"."sender_key", "t1"."session_id" ..." when send a simple message. #176
Comments
We have the same issues and it takes more than 5 minutes now. The database has 50MB now. Solved by removing the store & the credentials and then logging in again. |
The room in my case is a DM room. What I resolve this is leave the room to abandon the DM room, then create/join to a new DM room. But this way I have no history messages. :( |
Like mentioned in #180 try to hold it open and feed it with stdin instead of clearing all the crypto from mem, just leave it there and feed the open program with your messages. |
Reducing the number of applications starts is a neat trick and may work in some cases, but not in others. Even if you keep the program open for longer, after some time you'll run into the same issue again, as the store will still grow, just slower. |
In some cases |
For those who have flexibility, you might try the Rust version of |
I have a matrix synapse server 1.106.0 and this server is private only without federation.
I managed to use matrix-commander (7.6.1 2024-05-02) to send messages to an encrypted DM room. But the matrix-commander takes about half minute to complete.
The command I use is
The option
--log-level DEBUG DEBUG
is for debug only and then I got hundriespeewee: ('SELECT "t1"."id", "t1"."sender_key", "t1"."session_id"...
logs. And these took about 30 seconds.How can I avoid this problem ?
The text was updated successfully, but these errors were encountered: