![]() ![]() Check "Settings -> Download Clients" for your "Check For Finished Downloads Interval" - I'm sure this is not the issue, but I set mine to 1.Ĥ. Hover over the would-be importing/downloading icon to the left of the show/movie name in Activity section, does it say "Downloading" after deluge has marked it as "Seeding" and it is finished? or does it say "Waiting for Import" and gets stuck? Or an error of some sort (no files to import, etc)?ģ. Check you are using the latest version of the respective *arr's - however since it is both radarr and sonarr experiencing this, I'm not sure it truly is an *arr issue.I assume you have also hit the "Refresh" button in "Activity" and it remains stuck "Downloading".Ģ. I use *arr myself, and there are a few things you can check since it appears Deluge has marked these torrents as "Finished" best I can tell from the information at hand.I know this isn't an *arr support forum but since I have experience with them here's what I can suggest.ġ. Ltconfig for custom libtorrent settings in deluge - viewtopic.php?f=9&t=42887 Wslimit plugin for memory limits on libtorrent - viewtopic.php?f=9&t=56387 I would do a test download with sonarr or radarr and see what deluge is actually showing while sonarr and radarr report it not finished, if you haven't (you don't say whether you have) and report back. I use aio_threads between 10 and 16 depending on the disk's speed (traditional SATA SSD), and aio_max of 200.this may not be right for you though, do some research (google is your friend) - I think the default is 8 which is usually fine for traditional hard drives. You can increase the IO threads if you're using an SSD, as well as maybe try the wslimit plugin mhertz wrote to limit the amount of memory mapping done by libtorrent.this will take some tinkering and tweaking to get optimal results. ![]() not completed - for several minutes if not longer depending on the torrent's size. If the disk is not a SSD, this can be rather slow and it will remain "Downloading" - i.e. Libtorrent 2.x uses memory mapped files, which store as much of the file as it can in memory, rather than writing as it goes for the most part, so from my experience if you have your libtorrent settings set to defaults (not using something like ltconfig to change this - search the plugins section for this plugin and optimal settings) it will store a lot of the download in memory, sometime several GB's for larger files.then after finishing, write to disk. You didn't mention, but in deluge's UI - either standalone or thin client - does the torrent show as "Seeding" or is it sitting at "Downloading" after reaching 100% - possibly still writing from cache/RAM to disk. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |