remount: Increase scratch size from 50% to 85% of available data
adb remount clearly indicates that the user will use a scratch partition to modify RO content. In this CL we're trying to be more aggressive and take more space from data to scratch to improve the developers experience. Bug: 228945443 Test: launch cvd with updated value and check it reflects Change-Id: Ied9cee6e98d3b2dd594babcf213071a80bd3cf14 Signed-off-by: Dmitrii Merkurev <dimorinny@google.com>
This commit is contained in:
parent
057cbf6379
commit
9292c09c06
1 changed files with 1 additions and 1 deletions
|
@ -1083,7 +1083,7 @@ static inline uint64_t GetIdealDataScratchSize() {
|
|||
return 0;
|
||||
}
|
||||
|
||||
auto ideal_size = std::min(super_info.size, (uint64_t(s.f_frsize) * s.f_bfree) / 2);
|
||||
auto ideal_size = std::min(super_info.size, uint64_t(s.f_frsize * s.f_bfree * 0.85));
|
||||
|
||||
// Align up to the filesystem block size.
|
||||
if (auto remainder = ideal_size % s.f_bsize; remainder > 0) {
|
||||
|
|
Loading…
Reference in a new issue