-
Notifications
You must be signed in to change notification settings - Fork 612
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
sometimes slow response #550
Comments
There should be no significant difference in speed depending on the working directory. |
i think this issue from tqueue.binlog or cache fro working dir but i don't really so. |
None of these can cause significant difference in speed. |
I am experiencing the same issue, but switching the working directory hasn't made any difference. Specifically, both receiving requests and sending responses are extremely slow on the local server, and I'm unsure why this is happening. |
I think this issue from telegram datacenter's are slow or maybe on maintenance. But I'm not sure every week is slow at telegram datacenter's |
After deploying a local server, I understand that requests are forwarded and responses are handled by a local server proxy. How does this process relate to Telegram's data centers? |
you can check this diagram how to this lib work. Source : #1 (comment) |
@DoNotWannaTry The logs on the screenshot shows that everything works as expected. The only suspicious line is getUpdates request with timeout 0 instead of some big value, but this is an issue in the bot's code. |
I restarted the local server and re-registered the bots, and it seems to be normally now. |
hello, i got some issue after 2 - 3 weeks local server running.
after i change working directory parameter, bot will fast to response.
why it happened?
fyi, i use supervisor as daemon for keep local server running.
thank you,
The text was updated successfully, but these errors were encountered: