mirror of
https://github.com/sigma67/ytmusicapi.git
synced 2026-04-25 15:26:01 +03:00
[GH-ISSUE #230] Asynchronous requests #179
Labels
No labels
a/b
bug
documentation
enhancement
good first issue
help wanted
invalid
pull-request
question
wontfix
yt-error
yt-update
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ytmusicapi#179
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @georgetian3 on GitHub (Oct 1, 2021).
Original GitHub issue: https://github.com/sigma67/ytmusicapi/issues/230
I've implemented (a very hacky) implementation of ytmusicapi using
aiohttp, where performing 6 search queries decreased from 6 seconds without async, to 1 second with async.The speed improvements are great, but I understand some users may not wish to use async in their programs. With this in mind, would you be open to implementing async in the main ytmusic repository? Furthermore, letting the user choose between synchronous and async requests be an option?
@sigma67 commented on GitHub (Oct 3, 2021):
This is similar to parallelizing requests, which is something I would prefer to avoid as it might draw unwanted attention from Google (high server load due to much larger amount of requests in a short time window). However, feel free to publish your fork and link it here