On Thursday, March 5, 2015 at 8:42:34 PM UTC-6, Adrien Thebo wrote:
To me, following the principle of least astonishment indicates that
caching be disabled by default; it'll work correctly for new users and has
no hidden gotchas. When people want to do performance tuning they're
probably
The principle of least astonishment is absolutely what we should be
targeting. The use of any kind of timer upon whose ticks behavior changes
is in inarguable opposition to this, whether it's 10 seconds, 3 minutes, or
15 minutes. However, I think the use of implementation terms like caching
in
On Friday, March 6, 2015 at 11:36:03 AM UTC-6, Reid Vandewiele wrote:
The principle of least astonishment is absolutely what we should be
targeting. The use of any kind of timer upon whose ticks behavior changes
is in inarguable opposition to this, whether it's 10 seconds, 3 minutes, or
On Mar 6, 2015, at 9:06 AM, John Bollinger john.bollin...@stjude.org wrote:
On Thursday, March 5, 2015 at 8:42:34 PM UTC-6, Adrien Thebo wrote:
To me, following the principle of least astonishment indicates that caching
be disabled by default; it'll work correctly for new users and has no
As Eric said there seems to be clear consensus and an issue has been opened
to make the change. I think it is still be useful for me to respond in
detail to John, but just to wrap up the thoughts - not to further advocate
for reload behavior. There seem to be good reasons to choose to serve files
We've been discussing what the default environment_timeout setting should
be. There is general agreement that the current 3 minutes is not great.
It's both baffling to new users and does not bring in the full performance
benefits.
Two main perspectives on this:
1. Performance should be the
Can you use inotify to invalidate the cache via the API call when selected
files in your infrastructure change?
It looks like you could do this directly from the core
https://launchpad.net/inotify-java. You'll just want to queue them up a bit
to not go crazy. 10 seconds should probably do it, but
To me, following the principle of least astonishment indicates that caching
be disabled by default; it'll work correctly for new users and has no
hidden gotchas. When people want to do performance tuning they're probably
fairly sophisticated users and can deal with weird cache invalidation
issues;
This.
On 2015-03-06 03:42, Adrien Thebo wrote:
To me, following the principle of least astonishment indicates that
caching be disabled by default; it'll work correctly for new users and
has no hidden gotchas. When people want to do performance tuning they're
probably fairly sophisticated users
To clarify, I am asking for opinions on whether the default
environment_timeout should be 0 or unlimited in future releases of puppet.
The current plan is to default to unlimited.
I'm concerned that shipping with this default assumes prior experience and
will be another hurdle to getting
Oh...in that case I vote for unlimited *if and only if*, I don't have to
hack-fu my own script to clear the environment via an API call.
'puppet environment refresh' would be my recommendation.
Thanks,
Trevor
On Thu, Mar 5, 2015 at 8:19 PM, Owen Rodabaugh o...@puppetlabs.com wrote:
To
+1 to this suggestion.
-Eric
--
Eric Shamow
Sent with Airmail
On March 5, 2015 at 6:42:32 PM, Adrien Thebo (adr...@puppetlabs.com) wrote:
To me, following the principle of least astonishment indicates that caching be
disabled by default; it'll work correctly for new users and has no hidden
12 matches
Mail list logo
