xiaoyu

Members
  • Content Count

    8
  • Joined

  • Last visited

About xiaoyu

  • Rank
    New User

Recent Profile Visitors

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

  1. xiaoyu

    Latest Desktop Build 2.6.3

    So are there any rules which versions will be available for autoupdate?
  2. xiaoyu

    Latest Desktop Build 2.6.3

    Would you please update Debian repository? Thanks!
  3. xiaoyu

    Latest Desktop Build 2.4.5

    Will you update Docker image soon?
  4. xiaoyu

    [Solved] 100% CPU load on FreeBSD

    @Helen Looks like the issue has been fixed in 2.4.0. Now the CPU usage is always less than 20% even with more than 40 folders shared under FreeBSD. Thank you for all your great work!
  5. xiaoyu

    Resilio Sync 2.4 RC1

    @Helen I submitted a ticket.
  6. xiaoyu

    Resilio Sync 2.4 RC1

    OSX 10.11.6, CPU is very high after running for 30 minutes. Transfer speed is 0. Normally on 2.3.8, it was arount 40%.
  7. xiaoyu

    [Solved] 100% CPU load on FreeBSD

    After talking to Helen in support ticket, I found that it was because there were too many peers of my public sharing folders. Sync is keeping "ping" the peers to check whether they're still online. If there're hundreds offline peers, my node is waiting the "ping" responses until timed out. That costs too many CPU. (state umtxn and uwait) So is it possible in future to add a parameter to disable active "ping" to other peers. I think that will free up the waiting locks.
  8. Not sure if others have the same problem, but my FreeBSD Sync installation always takes 100% CPU load after it's running for a while. The web UI can't be loaded at all. I've already upgraded Sync to 2.3.8 In top it shows PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 79970 btsync 7 22 0 1065M 809M umtxn 3 553:54 100.00% btsync umtxn means Kernel Lock. So I ran # procstat -k 79970 PID TID COMM TDNAME KSTACK 79970 100367 btsync - mi_switch sleepq_catch_signals sleepq_timedwait_sig _sleep umtxq_sleep do_wait __umtx_op_wait_uint_private amd64_syscall Xfast_syscall 79970 100592 btsync - mi_switch sleepq_catch_signals sleepq_timedwait_sig _sleep umtxq_sleep do_wait __umtx_op_wait_uint_private amd64_syscall Xfast_syscall 79970 100594 btsync - mi_switch sleepq_catch_signals sleepq_timedwait_sig _sleep kern_kevent_fp kern_kevent sys_kevent amd64_syscall Xfast_syscall 79970 100602 btsync - mi_switch sleepq_catch_signals sleepq_timedwait_sig _sleep umtxq_sleep do_wait __umtx_op_wait_uint_private amd64_syscall Xfast_syscall 79970 100603 btsync - mi_switch sleepq_catch_signals sleepq_timedwait_sig _sleep umtxq_sleep do_wait __umtx_op_wait_uint_private amd64_syscall Xfast_syscall 79970 100605 btsync - <running> 79970 100607 btsync - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_lock_umutex __umtx_op_wait_umutex amd64_syscall Xfast_syscall Looks like a thread is locked. In the log, there're may SyncSocket errors. For example: [20160710 13:12:53.238] SyncSocket[0x0000000827bf4480]: an error has occurred - code: 61, message: "Connection refused" ZFS has been enabled in my Freebsd installation. Around 40 folders have been shared.