You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to puppet-users
Has anybody out there done any sort of study on what Puppet produces in terms of I/O packet rate? I'm being asked to fill in a spreadsheet with that information....
Christopher Wood
unread,
Jul 7, 2017, 3:45:48 PM7/7/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to puppet...@googlegroups.com
The answer is that it depends on your catalogs and what you're ramming through them. You might get a squinty rule of thumb measurement from figuring out the size of uploaded facts/report, downloaded catalog/files, add some more for random discussion traffic, divide by the number of seconds an agent run allegedly takes.
That said, you sound like you're living an even more corporate life than I am, and they might not take an answer of "it depends what you make puppet do".
You might also do a packet capture or some hypervisor i/o monitoring during an agent run, see how much that is and divide by the agent run time.
And then your numbers may turn out fictional when somebody decides they're going to ram tarballs in via file resource.
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to puppet...@googlegroups.com
I can share some rough numbers. We do a lot of files so the numbers are
weird and inefficient. Puppet 3.8.7/Passenger 5.1.5/Ruby 2.0/Apache 2.4
on the server side.
avg file metadata per puppetserver: 25k/s
avg hosts per puppetserver: 1200
avg catalog size: 15MB (lots and lots of files)
Peak TX rate: 4MB/s
Peak RX rate: 1.5MB/s
I'd suspect the average Puppetserver to be a fraction of that bandwidth
for the same number of hosts.
Ramin
Soham Chakraborty
unread,
Jul 8, 2017, 12:43:20 PM7/8/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Puppet Users, ramin...@badapple.net
Ramin,
I am interested to know how did you do the tests? I want to run a simulation myself.
Ramin K
unread,
Jul 8, 2017, 6:10:51 PM7/8/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to puppet...@googlegroups.com
Nothing fancy here. Parse the Apache log for /catalog/ to get catalog
sizes though you may need to tweak what you're logging, I'm using the
following, but only %b is needed to get bytes of the request.
http://httpd.apache.org/docs/current/mod/mod_log_config.html
File service metadata requests is parsing for "GET
/$some_env/file_metadata/". BTW in my stats that was 23k req/s if that
wasn't clear.
tx/rx is just from the interface. Nothing else on the box so it's all
Puppet plus general system stats collection, etc.
Ramin
> --
> You received this message because you are subscribed to the Google
> Groups "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send