Jump to content
Comet Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About TripleThreat

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I had tried the disk cache to 20G but that didn't help the reliability of BitComet at all. I will be switching to HBA this week. I hope that would improve BitComet's IO's.
  2. Thanks for the write up. I would definitely try to increase my disk cache size in my next restart and report back. Do you let BitComet to auto-choose cache size in the given range?
  3. I have left the disk cashe to default that is: Max cache size 1024 MB Max Disk Cach Size for LT Seeding: 1024 Shrink: 50MB I left my system.io.priority to normal and low.priority false. I have never experienced OS freeze but most definitely had BitComet program freeze. For 1.69 while starting 1000 tasks on top of 1000 active tasks would still render BitComet dead for 5 hours long and unable to recover, I can grow my active tasks to full 5000 tasks if I do it in batches (though it takes half a day). I have successfully left my computer over night the second try without crashing and I didn't change any setting at all. The memory grow seems reasonable now in 30G range as before it would likely grown into 50G range (don't quote me on this though). I think the way BitComet draws way too much IO when activating tasks at once without staggering. Hence, it put stress on the computer/chipset badly. I have just brought a HBA card. I would like to think it might help take the load off the computer/chipset but I am no computer guy. I also currently use a PCIE x1 SATA card. I think it might bottleneck the IO required for BitComet. I am going to remove that card once I have the HBA card installed and see if anything improves.
  4. Nevermind, first time I left 1.69 running overnight and the computer crashed. Found the computer blackscreen in the morning. Don't know if the cause of the crash was from BitComet, though very likely is.
  5. It could be but the interesting thing is if I ran the program for like 8 hours, the BitComet had no problem of shutting things down quickly. But if I ran the program for like two days, it would have problems shutting down. That is given I ran the same amount of torrent tasks and the same tasks in both scenarios. I think it is more due to RAM issue than anything. Speaking of 1.68, which I had problem running it and skipped back to 1.67. I ran 1.69 recently. It initially crashed a couple of times but then it became stable. That is I didn't restart computer in the trial to get it stable. Very interesting. I can vouch for 1.69. It is very NICE indeed.
  6. I have upgraded my main computer to WIn 10 but v1.68 still crashes my computer. Changes made to the options do not seem to work as starting a large batch of tasks would still halts BitComet to a stall and in need of a manual force quit.
  7. To give you another perspective, my other fresh Win 10 computer is currently running 12 upload tasks with 30G of actual files and with no active download tasks at 1.1GB of Ram and 3.0MB/s uploads.
  8. v1.68 is no good for me so I have downgraded back to the v1.67. I am finally going to upgrade to Win 10 once my new hard drives arrive. Then I will give v1.68 a try again. I am going to give your suggestions a try, Tin, and will report back. I have 950 EVO as my main drive and 128G of ram, so I think I can handle the changes. I do see the network_max could have been an issue for me since I have outdated router.
  9. With the current problems and critical bugs that have been plaguing BitComet for many versions now, 1700 tasks are no problem for the software 1.67 and those before it to handle. I have only count such crashes at 1.68. 1.68 crashes are actual crashes with Windows force quitting it by itself, while 1.67 and those versions before are so slow and unresponsive that Windows asks you if you want to give up and quit BitComet.
  10. Bitcomet 1.68 has been crashing extremely badly and renders itself unusable. I am only at 1700 active torrent tasks and left Bitcomet alone for like 10 minutes or so and it self would crash. That happened multiple times. 1.67 doesn't have this program. I use Windows 7.
  11. I have been using Bitcomet for more than five years plus and I don't recall I have ever encountered an data wipe due to update. I doubt there is any way to prevent it beside backing up the folder like the way you are doing it.
  12. I play the Google Chrome No Internet game 😞
  13. With the current bugs remaining on BitComet with the number of torrent tasks starting at the same time, I would like to see a build-in features to have BitComet stagger start batches of torrents with a time interval in between. It could act as a quick fix until the actually bugs have been resolved. Let say I highlighted 1000 torrents tasks and press start. BitComet would then start a first batch of 50 torrent tasks for you. Then after one minute it will automatically start another batch of 50 torrent tasks for you, until all of the 1000 tasks have started. I do have to say it seems like BitComet can handle 400 tasks start at the same time in the beginning. Once after that with 400 tasks have started and running, the program needs to stagger start torrent tasks, in order to run.
  14. You cannot blame us for trying 🙂
  • Create New...