Lines Matching full:we

5 let work build up so we can process it in more efficient batches, while also
9 usage is more important - we want to operate differently, with a "rush to
10 idle" so the system can go to sleep. We don't want to be dribbling out
24 When we implement idle detection and rush to idle, we need to be careful not
32 When the system is under continuous load, we want these jobs to run
42 For example, we don't want to run copygc too aggressively, because then it
44 deleted) anyways, and we don't want to wait until we're almost out of free
45 space because then the system will behave unpredicably - suddenly we're doing
51 When the system becomes idle, we should start flushing our pending work
62 It's important to let work accumulate when more work is still incoming and we
63 still have room, because flushing is always more efficient if we let it batch
67 On idle, how much work we do at each interval should be proportional to the
68 length of time we have been idle for. If we're idle only for a short duration,
69 we shouldn't flush everything right away; the system might wake up and start
71 work that would have been unnecessary if we'd allowed things to batch more.
73 To summarize, we will need: