Search the Community
Showing results for tags 'disk'.
Found 4 results
In ~/Library/Application Support/Resilio Sync on macOS I can see the SQLite databases being used to track shared folders. The WAL files are massive! In my case, for a share of two folders (having 1,654,405 files in many sub-folders) the entire folder is 2.86GB on each peer. About 1.1GB of that are wasted in WAL files while Resilio Sync is idle. I can appreciate the need for using SQLite to track files, but surely these WAL files can be periodically cleaned whilst Sync is idle? Or at least an effort to limit the maximum WAL size.
I set a sync VMWare virtual machines between my home and office computers (Win10). Syncing VM is very useful for me. The VM contain .vmx and .vmdk. And vmdk file is larger than 20GB. When I launch the VM. BTSync lock their files and start indexing. Then My SSD Disk encounter full load. Please refer the images, https://drive.google.com/file/d/0B-C2953cgRuuOUNKcWdDVWdlbG8/view?usp=sharing https://drive.google.com/file/d/0B-C2953cgRuuY2NjSGN6YS1ZZlE/view?usp=sharinghttps://drive.google.com/file/d/0B-C2953cgRuuaC1sM3BXMTJCejg/view?usp=sharing This makes slow other works on same computer. Even I "Pause syncing", BTSync process indexing the paused files. So I cannot help exiting BTSync service somtimes I feel PC is very slow. https://drive.google.com/file/d/0B-C2953cgRuuNm0tcU5nVzZOZms/view?usp=sharing On BTSync option, checked "Disk operations are low priority". I thought It can be a solution that disable indexing for locked files.
Hi, I'm on Windows 8 x64, BitTorrent Sync 1.0.116. While running the program, I've noticed some disk activity in the Resource Monitor I'm not sure I understand. From the Resource Monitor output it looks like BTSync.exe is constantly writing to my drive's MFT which doesn't seem to make all that much sense to me. If it's really doing it then why? Or maybe it's just some Resource Monitor / Windows API glitch and/or limitation and what it really does is reading MFT (polling it for file changes?). OTOH, the same seems to be the case when running chkdsk in read-only mode - the MFT operations are being reported as writes despite it's obviously the reads which actually happens. Anyone care to shed some light on this? Regards Zbig