Skip to content
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

What should be done to support the MTProto2 protocol? #2964

Open
2 tasks done
neo532 opened this issue Nov 1, 2024 · 3 comments
Open
2 tasks done

What should be done to support the MTProto2 protocol? #2964

neo532 opened this issue Nov 1, 2024 · 3 comments
Labels
feature request stale Issue had no activity. Might still be worth fixing, but dont expect someone else to fix it

Comments

@neo532
Copy link

neo532 commented Nov 1, 2024

Prerequisites

Description

Locust is very powerful. However, currently I want to conduct a load test on the MTproto2 protocol, but I'm struggling as I don't have a proper solution. I found the Telethon client on the Internet. Fortunately, it is also written in Python. But the combination of the two isn't going so smoothly. Could the official side please point out specific feasible solutions for reference? Thanks.

@cyberw
Copy link
Collaborator

cyberw commented Nov 2, 2024

Hi! I've never used MTproto2, but in general you'll find good instructions here: https://docs.locust.io/en/stable/testing-other-systems.html

@cyberw
Copy link
Collaborator

cyberw commented Nov 2, 2024

If you have a specific problem, let me know.

Copy link

github-actions bot commented Jan 2, 2025

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 10 days.

@github-actions github-actions bot added the stale Issue had no activity. Might still be worth fixing, but dont expect someone else to fix it label Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request stale Issue had no activity. Might still be worth fixing, but dont expect someone else to fix it
Projects
None yet
Development

No branches or pull requests

2 participants