search for: 1m30s

When I say winbind query I mean from `wbinfo -u` to a simple `getent passwd SAMDOM\\user`. When the winbind cache is small, clients that use a program in a network share of this server get timeouts while using the program, due to the cache expiring and the query to the PDC taking too, long. I've worked around that by setting a winbind cache time longer than the span of work hours and a cron

test/BugPoint/metadata.ll Takes about 6 seconds to run if llvm-symbolizer isn't present 13 seconds with debug info 1m30s with split DWARF/Fission So, couple of things: 1) llvm-symbolizer is /really slow/ on split-dwarf files... 2) Why are stack traces even attempted when using bugpoint? Even if it's just the 6->13s slowdown, that's still halving the speed of bugpoint in the presence of llvm-symbolizer+deb...

...e command manually? > > On Tue, May 23, 2017 at 2:02 PM, David Blaikie via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> test/BugPoint/metadata.ll >> Takes about 6 seconds to run if llvm-symbolizer isn't present >> 13 seconds with debug info >> 1m30s with split DWARF/Fission >> >> So, couple of things: >> 1) llvm-symbolizer is /really slow/ on split-dwarf files... >> 2) Why are stack traces even attempted when using bugpoint? Even if it's >> just the 6->13s slowdown, that's still halving the speed of bug...

...rity: minor Priority: P5 Component: Miscellaneous Assignee: unassigned-bugs at mindrot.org Reporter: ronf at timeheart.net While experimenting with the RekeyLimit option, I ran across a small bug in the convtime() function. When I entered a time value of '1m30s', I found that it converted this to 1860 seconds instead of the expected 90 seconds. Entering it as '30s1m' worked fine as a workaround (as would just entering "90"), but clearly the conversion is incorrect. The bug appears to be that the convtime() function doesn't reset...

...e mapped. On Mon, Jan 29, 2018 at 9:24 AM Leonardo Santagada <santagada at gmail.com> wrote: > > I cleaned up my tests and figured that the obj file generated with > problems was only with msvc 2015, so trying again with msvc 2017 I get: > > lld-link: 4s > lld-link /debug: 1m30s and ~20gb of ram > lld-link /debug:ghash: 59s and ~20gb of ram > link: 13s > link /debug:fastlink: 43s and 1gb of ram > link specialpdb: 1m10s and 4gb of ram > link /debug: 9m16s min and >14gb of ram > > link incremental: 8s when it works. > > > *specialpdb is creat...

I cleaned up my tests and figured that the obj file generated with problems was only with msvc 2015, so trying again with msvc 2017 I get: lld-link: 4s lld-link /debug: 1m30s and ~20gb of ram lld-link /debug:ghash: 59s and ~20gb of ram link: 13s link /debug:fastlink: 43s and 1gb of ram link specialpdb: 1m10s and 4gb of ram link /debug: 9m16s min and >14gb of ram link incremental: 8s when it works. *specialpdb is created with passing to a set of compilation units (...

...t 9:24 AM Leonardo Santagada <santagada at gmail.com> > wrote: > >> >> I cleaned up my tests and figured that the obj file generated with >> problems was only with msvc 2015, so trying again with msvc 2017 I get: >> >> lld-link: 4s >> lld-link /debug: 1m30s and ~20gb of ram >> lld-link /debug:ghash: 59s and ~20gb of ram >> link: 13s >> link /debug:fastlink: 43s and 1gb of ram >> link specialpdb: 1m10s and 4gb of ram >> link /debug: 9m16s min and >14gb of ram >> >> link incremental: 8s when it works. >&gt...

...;santagada at gmail.com> >> wrote: >> >>> >>> I cleaned up my tests and figured that the obj file generated with >>> problems was only with msvc 2015, so trying again with msvc 2017 I get: >>> >>> lld-link: 4s >>> lld-link /debug: 1m30s and ~20gb of ram >>> lld-link /debug:ghash: 59s and ~20gb of ram >>> link: 13s >>> link /debug:fastlink: 43s and 1gb of ram >>> link specialpdb: 1m10s and 4gb of ram >>> link /debug: 9m16s min and >14gb of ram >>> >>> link incrementa...

...>> wrote: >>> >>>> >>>> I cleaned up my tests and figured that the obj file generated with >>>> problems was only with msvc 2015, so trying again with msvc 2017 I get: >>>> >>>> lld-link: 4s >>>> lld-link /debug: 1m30s and ~20gb of ram >>>> lld-link /debug:ghash: 59s and ~20gb of ram >>>> link: 13s >>>> link /debug:fastlink: 43s and 1gb of ram >>>> link specialpdb: 1m10s and 4gb of ram >>>> link /debug: 9m16s min and >14gb of ram >>>> >...

...> >>>>> >>>>> I cleaned up my tests and figured that the obj file generated with >>>>> problems was only with msvc 2015, so trying again with msvc 2017 I get: >>>>> >>>>> lld-link: 4s >>>>> lld-link /debug: 1m30s and ~20gb of ram >>>>> lld-link /debug:ghash: 59s and ~20gb of ram >>>>> link: 13s >>>>> link /debug:fastlink: 43s and 1gb of ram >>>>> link specialpdb: 1m10s and 4gb of ram >>>>> link /debug: 9m16s min and >14gb of ram &...

I don’t have pgo numbers. When I build using -flto=thin the link time is significantly faster than msvc /ltcg and runtime is slightly faster, but I haven’t tested on a large variety of different workloads, so YMMV. Link time will definitely be faster though On Sun, Jan 28, 2018 at 2:20 PM Leonardo Santagada <santagada at gmail.com> wrote: > This part is only for objects with /Z7 debug

...;> >>>>>> I cleaned up my tests and figured that the obj file generated with >>>>>> problems was only with msvc 2015, so trying again with msvc 2017 I get: >>>>>> >>>>>> lld-link: 4s >>>>>> lld-link /debug: 1m30s and ~20gb of ram >>>>>> lld-link /debug:ghash: 59s and ~20gb of ram >>>>>> link: 13s >>>>>> link /debug:fastlink: 43s and 1gb of ram >>>>>> link specialpdb: 1m10s and 4gb of ram >>>>>> link /debug: 9m16s min a...

...t;>>> I cleaned up my tests and figured that the obj file generated with >>>>>>> problems was only with msvc 2015, so trying again with msvc 2017 I get: >>>>>>> >>>>>>> lld-link: 4s >>>>>>> lld-link /debug: 1m30s and ~20gb of ram >>>>>>> lld-link /debug:ghash: 59s and ~20gb of ram >>>>>>> link: 13s >>>>>>> link /debug:fastlink: 43s and 1gb of ram >>>>>>> link specialpdb: 1m10s and 4gb of ram >>>>>>> link...

The attached patch adds a new 'ConnectTimeout' option (man page updated in patch) to avoid wasting time when the target host is down. I needed that because I was using rsync/rdist over ssh for massive files update and the default connect() took too long for my purpose. The patch was tested on Linux only, but I used a similar one for ssh 1.2.XX on Linux, Solaris and HP-UX without

...cleaned up my tests and figured that the obj file generated with >>>>>>>> problems was only with msvc 2015, so trying again with msvc 2017 I get: >>>>>>>> >>>>>>>> lld-link: 4s >>>>>>>> lld-link /debug: 1m30s and ~20gb of ram >>>>>>>> lld-link /debug:ghash: 59s and ~20gb of ram >>>>>>>> link: 13s >>>>>>>> link /debug:fastlink: 43s and 1gb of ram >>>>>>>> link specialpdb: 1m10s and 4gb of ram >>>>&...

...>>>>>>> with problems was only with msvc 2015, so trying again with msvc 2017 I >>>>>>>>>> get: >>>>>>>>>> >>>>>>>>>> lld-link: 4s >>>>>>>>>> lld-link /debug: 1m30s and ~20gb of ram >>>>>>>>>> lld-link /debug:ghash: 59s and ~20gb of ram >>>>>>>>>> link: 13s >>>>>>>>>> link /debug:fastlink: 43s and 1gb of ram >>>>>>>>>> link specialpdb: 1m10s...

...ests and figured that the obj file generated with >>>>>>>>> problems was only with msvc 2015, so trying again with msvc 2017 I get: >>>>>>>>> >>>>>>>>> lld-link: 4s >>>>>>>>> lld-link /debug: 1m30s and ~20gb of ram >>>>>>>>> lld-link /debug:ghash: 59s and ~20gb of ram >>>>>>>>> link: 13s >>>>>>>>> link /debug:fastlink: 43s and 1gb of ram >>>>>>>>> link specialpdb: 1m10s and 4gb of ram &...

...>>> with problems was only with msvc 2015, so trying again with msvc 2017 I >>>>>>>>>>> get: >>>>>>>>>>> >>>>>>>>>>> lld-link: 4s >>>>>>>>>>> lld-link /debug: 1m30s and ~20gb of ram >>>>>>>>>>> lld-link /debug:ghash: 59s and ~20gb of ram >>>>>>>>>>> link: 13s >>>>>>>>>>> link /debug:fastlink: 43s and 1gb of ram >>>>>>>>>>> link sp...

...st { 192.168.1.120 } % nft -f incremental-ruleset-update * Fix monitor mode, ie. nft monitor, when reloading relatively large rulesets. * Fix transport matching in bridge when no context is provided, eg. % nft add rule bridge filter input tcp dport 22 * Parsing of time, eg. ct expiration lt 1m30s * Missing family when listing tables, ie. % nft list tables table ip nat table ip filter * Propagate error to shell on evaluation problems, eg. % nft add chain filter input { type filter hook inputt priority 0\; } <cmdline>:1:43-48: Error: unknown chain hook inputt add chain filt...

...;>>>>>>>>>>> with problems was only with msvc 2015, so trying again with msvc 2017 I get: >>>>>>>>>>>> >>>>>>>>>>>> lld-link: 4s >>>>>>>>>>>> lld-link /debug: 1m30s and ~20gb of ram >>>>>>>>>>>> lld-link /debug:ghash: 59s and ~20gb of ram >>>>>>>>>>>> link: 13s >>>>>>>>>>>> link /debug:fastlink: 43s and 1gb of ram >>>>>>>>>>...