Search the Community

Showing results for tags 'cpu usage'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  1. Thank You! Thank You! Thank You! I just updated from v2.4.4 of Resilio Pro to v2.5.6 of Resilio Home Pro and what an AMAZING IMPROVEMENT!!! From the very first install of the paid version of the program on three of my computers back in February, ALL but one of them ground to a halt every time I left Resilio running and syncing in the background. Admittedly I am syncing upwards of 30 top-level folders, with some containing hundreds, if not thousands, of multiple sub-folders and being over 1GB in total size. But like I told tech support at the time, I was doing the same previously with "Cubby" and never had a single problem. So I purchased new and more RAM for each of the three machines, max'ing them out at between 16 and 32 GB each. Didn't help. Even upgraded the CPU on one machine and pushed the overclocking of the CPU even further on another machine. Still no difference. I was relegated to running Resilio and allowing the machines to sync ONLY during the overnight, as each morning when I grabbed my mouse, it was like pushing thru frozen molasses on the screen... not even during the early days of the original 8086 was it this bad. I was forced to reboot the computer and promptly shutdown Resilio; which of course didn't help during the daytime hours when I needed mission critical files to be synced as they were changed and updated. Like I said, I was ready to abandon all hope... when, like magic, I updated to v2.5.6 and ALL is finally working like it should! No more resource, CPU or RAM hog! I now leave Resilio running all day and night, 24/7, with never a slowdown in sight! What a pleasure! I'm now firmly on-board with Resilio. Thank You developers for LISTENING, finally recognizing, addressing and ultimately fixing this problem! (Resilio could probably now run even on a "Model T" Intel 8086-powered IBM Jr.!) So again, THANK YOU! THANK YOU! THANK YOU! ...now please don't go messing it up in future updates, And lastly, BTW, to whom can I send my bills for the unnecessary RAM & CPU upgrades? ...ha! ha! Respectfully, PJS
  2. Hello BtSync usually uses one Core with full load, often in quite bad moments, meaning when I am waiting for programs to start up. Therefore I would like to limit of CPU usage. How can that be achieved in Windows? br nana
  3. Attached are some samples and debug logs. I love BTSync, but it's really killing the battery on my laptop, with constant CPU usage. Let me know if you need anything at all, I'm happy to quickly attach! Thanks! sample.txt sync.txt
  4. Since starting to use the BitTorrent Sync app with large amounts of files--15GB and 20,000 files is a lot for Android--my phone periodically goes into 4-5 hours long episodes of 30-40% CPU usage. This wipes out the battery far faster than an S4 should normally perform. I've determined that it's due to Android's Media Server running overtime. I've seen people reporting this unfortunate activity from Media Server as inevitable when you have lots of files, but that placing a ".nomedia" file in a directory will make Media Server ignore everything under that file hierarchy. I've done this with all my BitTorrent Sync folders, but I still get periodic, out-of-control episodes of Media Server battery hogging. They seem to always correspond to times when I've made lots of file changes, so that Media Server would have a lot to do if it was not properly ignoring the trees from a ".nomedia" file on down. In that case, it seems like the .nomedia directive has less than a full effect. I was wondering about other people's Android battery experiences. It's certainly not the fault of the BitTorrent Sync process itself, as that has been thoroughly investigated, and I'm using its sleep function. So this is really an Android question, but I'm more likely to find Android users of BitTorrent Sync here than BitTorrent Sync users at the thread I started at xda. I'm a little concerned, though, that the number of Android users here is so small that the problem becomes intractable when it comes to treating your Android/BTSync config like a regular computer to the degree that phone users are forced to implement syncing on limited sets of files. Any suggestions and insights on efficient use of BTSync on phones in general would be welcome, including iPhone. I mean, I'd seriously entertain switching to iPhone if I could keep all my stuff in sync and still regularly get a full day's use out of my phone's battery.