mirror of
				https://github.com/Zygo/bees.git
				synced 2025-11-04 04:00:36 +01:00 
			
		
		
		
	README: we have multiple worker threads now, so don't say that we don't
Signed-off-by: Zygo Blaxell <bees@furryterror.org>
This commit is contained in:
		@@ -134,11 +134,6 @@ performance by caching, but really fixing this requires rewriting the
 | 
				
			|||||||
crawler to scan the btrfs extent tree directly instead of the subvol
 | 
					crawler to scan the btrfs extent tree directly instead of the subvol
 | 
				
			||||||
FS trees.
 | 
					FS trees.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
* Bees had support for multiple worker threads in the past; however,
 | 
					 | 
				
			||||||
this was removed because it made Bees too aggressive to coexist with
 | 
					 | 
				
			||||||
other applications on the same machine.  It also hit the *slow backrefs*
 | 
					 | 
				
			||||||
on N CPU cores instead of just one.
 | 
					 | 
				
			||||||
 | 
					 | 
				
			||||||
* Block reads are currently more allocation- and CPU-intensive than they
 | 
					* Block reads are currently more allocation- and CPU-intensive than they
 | 
				
			||||||
should be, especially for filesystems on SSD where the IO overhead is
 | 
					should be, especially for filesystems on SSD where the IO overhead is
 | 
				
			||||||
much smaller.  This is a problem for power-constrained environments
 | 
					much smaller.  This is a problem for power-constrained environments
 | 
				
			||||||
 
 | 
				
			|||||||
		Reference in New Issue
	
	Block a user