[chef] RE: Re: Re: Re: RE: Re: RE: Re: RE: RE: Re: chef server load testing


Chronological Thread 
  • From: Marcus Simonsen < >
  • To: " " < >
  • Subject: [chef] RE: Re: Re: Re: RE: Re: RE: Re: RE: RE: Re: chef server load testing
  • Date: Fri, 27 Mar 2015 19:52:46 +0000
  • Accept-language: en-GB, en-CA, en-US

Here are my musings on the subject if anyone is interested:
https://github.com/marcusbb/chef-client-jmeter

There are 2 general approaches I took. 
1. Write a JMeter plugin calling instances chef-client
2. Wrap the Chef server api in some concurrency operations

Feel free to mock me :)  But I wouldn't mind constructive feedback either.


From: Marcus Simonsen
Sent: 13 March 2015 18:53
To: Peter Burkholder;
Subject: [chef] Re: Re: Re: RE: Re: RE: Re: RE: RE: Re: chef server load testing

Ya been thinking about it, and I will look into it. 
It's even possible that I'll create the necessary concurrent and reporting features that I need in ruby. 
But it's likely I need a coordinated cluster of client bots to hammer the server., which JMeter provides. 
Combined with my comfort with JMeter and java I simply don't want to re-invent, rather than to bridge technologies.

Sent from my BlackBerry 10 smartphone on the Bell network.
From: Peter Burkholder
Sent: Friday, March 13, 2015 6:04 PM
To:
Reply To:
Subject: [chef] Re: Re: RE: Re: RE: Re: RE: RE: Re: chef server load testing

Markus,

Would it be worth considering a Ruby load-testing framework? Alas, the only one I know if is: https://github.com/brewster/front_end_loader

-Peter





--

Peter Burkholder — Customer Success Engineer

Unavailability: Travel March 2-3; Vacation March 16-20; ChefConf March 30-April 3

301-204-5767 –  " target="_blank">  – my: Linkedin  Twitter  Calendar

CHEF

CHEF.IO

TM

chef.io   Blog   Facebook   Twitter   Youtube  





Archive powered by MHonArc 2.6.16.

§