Searched refs:tolerable (Results 251 – 275 of 723) sorted by relevance
1...<<11121314151617181920>>...29
322 computation, so the overall performance impact of the barrier is tolerable.
881 method of manual refresh is tolerable so I won't pursue the 10-second
1666 used to ensure a particular request's performance is within a tolerable range.
755 While this is tolerable as long as only short-running commands are
383 …t pull requests that significantly decrease coverage (less than 1% decrease is sort of tolerable).
34 % Not: don't inline TE_read for USE_HEXD (15*5 bytes for ACSO0g is not tolerable)
106 tolerable efficiency:
649 While this is tolerable as long as only short\-running commands are invoked on
1226 the overall performance. The loss of precision is tolerable until the
583 While inaccurate integration is usually tolerable for elliptic problems, for
843 configured determines the amount of tolerable data loss.
14 which is rational is tolerable.
5954 tolerable 1 容許
520 marks is considered tolerable.
453 …uld have to write ``mlr put 'begin{@sum = 0}; @sum += $x'`` -- which is tolerable -- but for ``mlr…
581 …ot __fish_seen_subcommand_from $cmds" -a migrate-setmaxdowntime -d "Set maximum tolerable downtime"584 …ot __fish_seen_subcommand_from $cmds" -a migrate-getmaxdowntime -d "Get maximum tolerable downtime"