limiting concurrent sessions about g10k HOT 10 CLOSED

Thanks for your kind works, I know g10k still has some rough edges, but we like the performance increase very much :)

We are using a single server in front of all Puppetservers that runs g10k once and then rsync all Puppet environments to the Puppetservers instead of triggering g10k on each Puppetserver.
Otherwise running almost 100 Puppetserver would/should trigger DDOS protection on the Puppetlabs Forge or github.com anyway, besides wasting resources.

I added limitation of the maximum number of goroutines running for Git/Forge resolving.

Try it out.
https://github.com/xorpaul/g10k/releases/tag/v0.2.8b
db95104

from g10k.

it would have been easier to add options if you used docopt (it exists either for Pytthon and for Go).

from g10k.

it's impressive! With the older version I was able to fetch in 8 seconds, with this new version I am able to fetch in 2 seconds

from g10k.

Wow, are you sure that your not just using the cached Git and Forge modules now?
Was it really the overload of your Gitlab server that slowed down your previous g10k runs?
How many workers are you using right now?

from g10k.

I didn't set the worker limit right now (as I don't have the 2nd puppet server yet), but I played a bit with it and I have seen a strange behavior when I set it to a very low value (a meaningless value, lower than 5).
In this case it throws an error, saying that it cannot connect to my Gitlab server (with the usual error message: please check if you have put you keys... ).
The other difference, is that now I used the binary compiled by you, while in the previous case, I compiled the binary on a RedHat 6 (which means that I surely used some older version of Go).

from g10k.

Hi. I have been working on this:
https://github.com/maxadamo/g10k-webhook (until I decide to move everything on the public Gitlab).
It's a drop-in replacement for r10k_gitlab_webhook, enhanced with a lot of steroids.
it would have been nicer to to it with Go, but it would have taken ages compared to python.

Honestly, I don't understand if it's good for generic use, of if it fits too much my environment.

from g10k.

This would be useful for me too.

from g10k.

I still need to find a bug introduced by db95104 before I can merge it.
For some reason it waits indefinitely for a go routine.

from g10k.

Found the bug, missing waitgroup 19b953d#diff-b112433c20987b983fa33aa1eac9482dR58

Relase: https://github.com/xorpaul/g10k/releases/tag/v0.3.7

from g10k.

Seems like the -maxworker parameter has never worked.

It should be fixed now with v0.7.1

#141

from g10k.