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
LogFormat "%v %V %{X-Forward
Ramin,
I am interested to know how did you do the tests? I want to run a
simulation myself.
On Saturday, July 8, 2017 at 3:44:26 AM UTC+5:30, Ramin K wrote:
>
> On 7/7/17 9:52 AM, Peter Berghold wrote:
> > Has anybody out there done any sort of study on what Puppet produces in
> > terms of I/O
On 7/7/17 9:52 AM, Peter Berghold wrote:
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
I can share some rough numbers. We do a lot of files so the numbers are
weird and inef
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 ag
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
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group
