If I pause the 80GB transfer, the app goes back to 3% processor use (despite having 1500 torrents available for seeding). I haven't been using the nightly and can't afford to break anything right now, I just wanted to confirm the malfunction on my side, while it's been working very well with smaller torrents until now (and v3 didn't have this issue either). On the activity monitor for the Transmission app, memory seems totally normal (around 350MB), processor is around 60% and I think that's unusually high. A few seconds later it's fine, but if I wait a bit or click anywhere it goes back to beach ball. When I click on the icon to display the app, it takes a few seconds before displaying the app, I get the beach ball and the activity monitor says the app isn't responding. With an 80GB file, it's not working properly. I'm using an intel Mac (2017) on Ventura 13.2ĭownloading small torrents (like a few GBs) works perfectly. However, sporadic pinwheeling/beach-balling got noticeably more frequent with the nightly. Update: I tried the nightly build and that fixed the dropping-peers and slow download issues. But even in those cases, it seems to be entirely dependent on finding 1-2 really fast peers instead of being able to pull from the full swarm. But then others, every once in a while, I might still get, say, the entire file in 20 minutes (still slow compared to how I would've previously gotten the same file in 2-3 minutes, but still a lot faster than the new normal of Transmission 4.0). Some torrents will hold on to up to 5 peers, others can't hold on to any. It's not entirely consistent - some torrents that previously would've taken only minutes to download are now taking hours or even days. Some downloads drop to zero peers (even though there are plenty available) and won't reconnect unless I restart Transmission - then the cycle repeats itself. I'm lucky now when Transmission 4.0 is able to hold on to 1-3 peers at a time. Primarily, in my case, this seems to be from most peers getting dropped.Į.g., I start a new download, a dozen or more peers will connect from the swarm, Transmission will indicate it'll take about 4 minutes to download, and then peers will start dropping like flies. I haven't run into any UI slowdowns with Transmission 4.0 - but I have started hitting massive slowdowns in download speeds. The application is running as it had been before I had updated. I decided to revert back to v3.0.0, and have zero issues with having done so. Sorry to hear about your and everyone’s issues with v4.0.0. I'm on Ventura 13.2 with Transmission 4.0.0 If you can suggest any better ways to diagnose this please let me know. I am checking htop and activity monitor when it's pinwheeling but it seems to only be using a few % of CPU on a single thread, so I think it is waiting on something but not sure what the issue is. This primarily happens when something is being downloaded or uploaded I just completed a download and its now scrolling without any issue. I just updated from V3 to V4.įor devs: essentially any action in the GUI (scrolling, clicking file, etc.) will cause the app to pinwheel, sometimes for a second or two, sometimes for >30 seconds. I am getting read/writes >200 mb/s so I don't think this is the issue, but I am not sure how else to better diagnose the cause of this issue. This is on a New Mac Mini M2 (2023) with reasonably fast external disk connected via USB-C. About 200 transfers going and the interface pinwheels after about every click.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |