![]() By active I mean either in a seeding state or a downloading state, but not including queued and stopped. Generally speaking the amount of Java heap memory required is related to the number of active downloads you have. Burning up a little more RAM to take some of the load off your hard drive would be about the best correction you could make. ![]() Some of the things I've mentioned may conceivably increase BiglyBT's RAM usage somewhat, but in all honesty my read of your performance screenshots says that'd be a good trade. (I do have the "Don't count." values set to 50 kB/s and 15 kB/s, though, to make sure that basically-inactive torrents don't prevent well-seeded ones from starting.) I keep mine at 4 and 6, respectively, because I find that if I have any more than that going, they just end up starving each other and they all take longer than they should. In Options > Queue, setting maxes on simultaneous downloads & active torrents can be a big help.All three "Maximum." options can help to limit both memory growth and disk contention."Perform read-aheads." and "Cache download data." you likely want."Size of cache in MB" (As it says, no more than 32MB, but you probably want the full 32MB)."Enable disk cache" (You for sure want that).In Options > Files > Performance Options.Some items of particular interest, affecting disk load: I'd recommend also looking over Options > Files, Options > Files > Performance Options, and the Options > Queue settings that affect the number of concurrent torrents that can be down/uploading at the same time. (It could still be BiglyBT, say performing post-startup rechecks and other torrent data operations, which can cause a great deal of disk activity particularly at startup, but there are techniques for mitigating that as well.) That filesystem load is concerning, though - unless it was a one-time fluke, like when those screenshots were taken you happened to be copying a folder full of multi-gigabyte MP4 files from one partition to another, or whatever.īut if that's a normal occurrence, personally I'd want to find out what's causing it and address that issue. The stats on memory all look positively idyllic. buuuuut, I'd personally be shocked if it made any appreciable difference because there's very little indication (to my eye) that the CURRENT RAM consumption is in any way a problem for your system. That may be a bit of an exaggeration, but sustained filesystem loads of 80%-95% are not something I'm used to seeing under remotely normal circumstances, even with a traditional spinning-rust (non-SSD) drive.īy all means, follow Parg's advice (he wrote the bloody thing, you'd be a fool not to!) and look into options for reducing BiglyBT's memory footprint. Not that you don't NEED the cache, because something apparently hates your hard drive(s) and is trying to murder it/them! Hm, OK, yeah, that's about what I'd expect to see regarding CPU and memory - TBH you've got memory to spare, and then some, only about half of your 8GB is even in use.
0 Comments
Leave a Reply. |