David Baggerman

That is a good point. However, one concern I'd have with that is that cronjobs can only run once per minute. An agent could accept and fail a number of...

To clarify a bit, the cronjob solution would work well for a preventative shutdown under normal/predictable use. That's useful but I'm also concerned about builds that create problems very quickly...

> I assume most elastic stack users rely on the instances self-terminating after the idle timeout to avoid similar issues - does that work less effectively for you because you...

> We had this problem on jenkins and the cloud node plugin has a feature to terminate the instance after x builds have run. We set it to 100 builds...

> Isn't there a lifecycle hook in the stack that allows jobs to finish before continuing the termination ? If so, I believe the instance refresh respects this... but perhaps...

Hi @foxdd, I _think_ I considered using this type of map lookup when I was implementing the bloom filer, but I can't remember why I ended up going with the...

@foxdd, I think the problem with the current implementation is the condition inside `shouldProcess`. Since `shouldProcess` gets called for every byte of every file, it's having to ask "should I...

``` Benchmark #1: ./scc-master --no-complexity=false golang/go Time (mean ± σ): 100.4 ms ± 4.4 ms [User: 807.0 ms, System: 208.1 ms] Range (min … max): 94.0 ms … 113.2 ms...

Benchmarked with file readers and directory walkers set to different values. This is on a quad core (8 thread) laptop which would run 32 readers with the current default. For...

> I am more in favor of the ulimit one if possible. Agree it might not be cross-platform. It's possible, at least on POSIX systems (I don't have a clue...