mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Enable OS cache (enabled by default) - hight interdisk link load, low speed. #6434
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#6434
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @shevalier on GitHub (Nov 26, 2017).
Please provide the following information
qBittorrent version and Operating System
4.0.1 amd64 Windows 10 amd64 FCU
If on linux, libtorrent and Qt version
(type here)
What is the problem
Enable OS cache - enabled by default.
If user have for peering physical dedicated disk(HDD/SSD), qbittorrent load data to system disk in temp folder ("Downloads)", then copy to dedicated. All disks gets load at 100%, download speed - to 0.
What is the expected behavior
Enable OS cache - disable by default for multidisk environment
Steps to reproduce
system and storage on physically different disks
Extra info(if any)
(type here)
@xavier2k6 commented on GitHub (Sep 30, 2019):
@shevalier Try 4.1.8 & report back.
@ghost commented on GitHub (Jul 25, 2022):
This issue has been closed for being too old, and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.