Jump to content
Comet Forums

cavedog8

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About cavedog8

  • Rank
    Seeder

Recent Profile Visitors

834 profile views
  1. Been using BitComet for ages. There is NO better client. The LTS setup is unique delivery real speed increases that other clients just can't give and I tested a whole bunch of them and uninstalled them all. So thanks a lot to all involved. Now that said I'm looking at the Best disk cache settings. Setting it on default is problematic with a fast connection. So i set the max to be 7GB and yes that maxes my 200Mbps line almost always I feel that 7GB is high especially when bitcomet tends to want to use the whole 7GB. Reducing this reduces the amount Bitcomet uses but large torrent downloads go slower then and Disk IO increases which is causing the slower downloads. What are you guys setting it as and what internet speed do you guys have? Some feedback would be appreciated. Thanks Also Bitcomet feels a bit sluggish when it's downloading at 22MB/s. Is it just me?
  2. I know I have seen the LT Seeding column before and it showed which torrent is actually LTS seeding and the speed. Is it on the old versions or does the new version have it too because I can't see it. I can see in the top that my upload speed is 14256kB/s so basically maxing my upload speed and all my bt tasks is stopped so it's LTS seeding which I actually don't mind at all but I do remember you could actually see it as a LT Seeding column.
  3. Since my last post I've been trying everything and seems like if I want to seed these 3 torrents @ full 100Mbps aka ~13MB/s I would need a disk cache setting of at least 5GB. Find it strange that BitComet needs this much RAM to seed at full 100Mbps. Now I just wonder what will happen once I start adding more torrents and they start seeding too. RAM usage would then skyrocket.... These torrents have been moved to my SSD and everything is running from my SSD.
  4. Thank you for your reply. I assure you there is no confusion here. I know the difference between MB/s and Mbps. 100Mbps is give or take 12.5MB/s depending on TCP overhead. I can assure you it's a bitcomet issue and I decided to test other client with the exact same 3 torrent seeding on the same hdd but not seeding the same time as each other. For the test I closed bitcomet and rehash checked the 3 torrents in qbitorrent. I have attached it below. You can see my line is almost being maxed but the disk read is not being killed like in bitcomet. My main drive is a CRUSIAL MX500 250GB SSD and it's still being overworked. Disk read speeds on the the SSD of 190MB/s Not sure why bitcomet is reading so many pieces of the same file at the same time. I have 16Gb RAM. Increased the cache to 6GB and that 6GB got eaten up so quickly then uploads slowed to a crawl again. My main question is why is bitcomet doing it but others like Deluge and qBittorrent not..... Always been a fan of bitcomet but never had this problem before.... I'm going to downgrade and see if I still get the same issue. Something is causing the disk io to be so high and I want to find out why.
  5. So basically I added a 1TB HDD to my pc to use only for BitComet. Downloaded 3 torrent. 1 x 50GB, 1x 35gb and 1x 10Gb torrent. I have a 100Mbps download and upload fibre line. Torrents downloaded @ 12Mb/s which is very good as always. Now I left these torrents seeding and found it strange that they are only seeding @ like 800KB/s. Noticed bitcomet is very slow to respond and see that when I check task manager BitComet is using the Disk at 100% and read speed of 85MB/s but everything is only seeding at less than 1MB/s so why is Bitcomet killing the Disk IO like that? Task manager shows Network is only being used at 4Mbps aka 450KB/s upload but the disk with 3 torrent files is being killed by bitcomet. Using bitcomet 1.49
×
×
  • Create New...