[
https://issues.apache.org/jira/browse/CASSGO-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
João Reis updated CASSGO-90:
----------------------------
Description:
In 2.0.0-rc1 we got rid of query object pooling so the extra allocs associated
with QueryMetrics are unnecessary when query metrics are not even being used by
the user and I believe the majority of users isn't using them so making them
opt-in makes more sense.
In this context Query Metrics are associated with the methods:
* Iter.Latency
* ObservedQuery.Metrics
* ObservedBatch.Metrics
was:
In 2.0.0-rc1 we got rid of query object pooling so the extra allocs associated
with QueryMetrics are unnecessary when query metrics are not even being used by
the user and I believe the majority of users isn't using them so making them
opt-in makes more sense.
In this context Query Metrics are associated with the methods:
* Iter.Latency
* ObservedQuery.Metrics
* ObservedBatch.Metrics
> Make QueryMetrics opt in
> ------------------------
>
> Key: CASSGO-90
> URL: https://issues.apache.org/jira/browse/CASSGO-90
> Project: Apache Cassandra Go driver
> Issue Type: Improvement
> Components: Core
> Reporter: João Reis
> Assignee: João Reis
> Priority: Normal
> Fix For: 2.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In 2.0.0-rc1 we got rid of query object pooling so the extra allocs
> associated with QueryMetrics are unnecessary when query metrics are not even
> being used by the user and I believe the majority of users isn't using them
> so making them opt-in makes more sense.
> In this context Query Metrics are associated with the methods:
> * Iter.Latency
> * ObservedQuery.Metrics
> * ObservedBatch.Metrics
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
