Searched full:significantly (Results 1 – 25 of 354) sorted by relevance
12345678910>>...15
50 /// if it significantly slows down compilation or would prevent even basic77 /// This mode is significantly more aggressive in trading off compile time86 /// order to make even significantly slower compile times at least scale
249 and context switch overhead did not change significantly255 The times for the use of pipes are significantly higher under287 These results show that passing argument data is significantly332 be significantly less.442 significantly longer than under 4.1BSD. System profiling shows528 of the buffer cache may be reduced significantly on memory-poor547 This figure can vary significantly depending on
275 /// bug path significantly shorter.287 /// bug path significantly shorter.303 /// bug path significantly shorter.316 /// bug path significantly shorter.330 /// bug path significantly shorter.
93 The larger values can significantly increase system performance in some118 significantly (5-10 times) greater than the default hash table size (257).
41 * plugin to this interface is significantly easier than stacking kdb42 * modules. Also, the kadm5 interface is significantly more stable
119 cache can reduce the number of I/O operations significantly.177 data sets can produce significantly reduced tree sizes and search times.
10 provide significantly less accuracy than portable equivalents then a clear
40 /// already-compared bytes. This must be significantly118 // version is sometimes significantly faster and sometimes in lzma_memcmplen()
66 cache can reduce the number of I/O operations significantly.148 data sets can produce significantly reduced tree sizes and search times.
7 significantly until a final implementation is drawn up.
28 This is significantly cheaper than INCP, and since OFF is not
33 This is significantly cheaper than INCP, and since OFF is not
39 …sanitize=address), but be aware that using Address Sanitizer may also significantly reduce perform…
56 is significantly larger in size.
162 the interface was significantly rewritten.
30 # Test scenario: Last memory domain significantly smaller than the others.
22 cache flush/invalid actions, and improve the performance significantly.
48 cache flush/invalid actions, and improve the performance significantly.
49 well as significantly decrease the amount of spam that arrives at your
46 // significantly on memory accesses, as well as 1K of CRC32 table, on platforms
10 XZ Utils compress some files significantly worse than LZMA Utils.
5 significantly faster.
10 // execute short instructions significantly faster than longer instructions.
101 so the low-order bits should no longer be significantly worse than the
150 and significantly rewritten by