#The problem of memory consumption
8 messages · Page 1 of 1 (latest)
To be honest, I checked it out
I'll check right now.
Memory usage is maintained at 52 MB, even though all workers are running for tracking purposes.
Perhaps I am not looking in the right place, but I launched the bot from the console
!s
before I mark this thread as solved, did you fix it? what was the issue?
The problem was a critical bug in the library used cloudscraper by VeNoMouS, in which, as I understand it, after each request, all data was stored in the RAM cache, which led to excessive consumption.
I managed to fix it thanks to a fork of cloudscraper by zinzied that supports the library and, importantly, added asynchrony, which allows it to work within asynchronous applications and not block the thread.
nice! next time don't delete your post! other users can search for it when they stumble across the same issue 😉