Anyone know why we keep intermittently dealing with this suspect string in
dunit tests?
I think we need all valid ways of starting up a Locator to be in a state
that NEVER produces this NPE. But I'm not sure how to fix it because I'm
not familiar with startClusterManagementService. Some pointers o
I think this may only occur in tests that perform a reconnect of the
Locator.
On Fri, Jan 10, 2020 at 9:06 AM Kirk Lund wrote:
> Anyone know why we keep intermittently dealing with this suspect string in
> dunit tests?
>
> I think we need all valid ways of starting up a Locator to be in a state
Is there a specific test that would cause this NPE? I will try to take a
look at it.
On Fri, Jan 10, 2020 at 9:08 AM Kirk Lund wrote:
> I think this may only occur in tests that perform a reconnect of the
> Locator.
>
> On Fri, Jan 10, 2020 at 9:06 AM Kirk Lund wrote:
>
> > Anyone know why we k
Hi geode-dev,
We have executed some traffic against Geode servers with time-based statistics
enabled and disabled and we didn't see any performance difference.
The documentation says:
If you need time-based statistics, enable that. Time-based statistics require
statistics sampling and archival
I personally wouldn't be too worried about enabling time based statistics
in production. I think we segregated the time statistics because they do
have to call System.nanoTime to measure the elapsed time. At one point in
the history with old JDKs they called System.currentTimeMillis, which was
real
When we were doing Micrometer work we confirmed that enable-time-statistics
doesn't change performance. We'd like to deprecate this property and turn
it on always.
On Fri, Jan 10, 2020 at 12:45 PM Dan Smith wrote:
> I personally wouldn't be too worried about enabling time based statistics
> in p
The biggest impact was in recording all the additional stats in the old
blocking stats implementation. As of 9.8 the stats internals are mostly
non-blocking. Enabling time stats has very little of any impact now.
> On Jan 10, 2020, at 12:45 PM, Dan Smith wrote:
>
> I personally wouldn't be to
Sounds like the caveat could be dropped from the user guide. If we have
consensus on that (am I understanding correctly?), I'll initiate a JIRA
ticket.
On Fri, Jan 10, 2020 at 1:47 PM Jacob Barrett wrote:
> The biggest impact was in recording all the additional stats in the old
> blocking stats
Read that as “As of geode 1.9.0 …”.
Anthony
> On Jan 10, 2020, at 1:19 PM, Jacob Barrett wrote:
>
> The biggest impact was in recording all the additional stats in the old
> blocking stats implementation. As of 9.8 the stats internals are mostly
> non-blocking. Enabling time stats has very li
David,
I would say remove the caveat.Thanks for offering.
Charlie
On Fri, Jan 10, 2020 at 1:55 PM Dave Barnes wrote:
> Sounds like the caveat could be dropped from the user guide. If we have
> consensus on that (am I understanding correctly?), I'll initiate a JIRA
> ticket.
>
> On Fri, Jan
10 matches
Mail list logo
