Bohdan Siryk created CASSGO-89:
----------------------------------
Summary: Performance regression due to CASSGO-1 changes
Key: CASSGO-89
URL: https://issues.apache.org/jira/browse/CASSGO-89
Project: Apache Cassandra Go driver
Issue Type: Task
Components: Core
Reporter: Bohdan Siryk
> Hey all. Trying to track down an issue, which is appearing when switching
> the version of the Go driver. The team I'm working with has narrowed it down
> to this
> [commit|https://github.com/apache/cassandra-gocql-driver/commit/63b6d7830710a0c6c5411c08bf16d38cb88d2a8a#diff-4f427d2b022907c552328e63f137561f6de92396d7a6e8f6c2ea1bcf0db52654].
> They bumped the driver version to that commit & pinned the protocol to v4.
> They're seeing a massive increase in allocation and increased latency. The
> memory allocation isn't actually coming from the driver, but rather later in
> the stack where it creates a protobuf object. Based on the network traffic,
> there's a lot more data coming back to the client than there was before.
Originally raised in
[https://the-asf.slack.com/archives/C05LPRVNZV1/p1756169350344849]
Potential regression due to changes brought by CASSGO-1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
