[
https://issues.apache.org/jira/browse/CASSANDRA-17947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612440#comment-17612440
]
Blake Eggleston commented on CASSANDRA-17947:
---------------------------------------------
I'd prefer we keep this around for now if it's now causing any issues for us. I
do intend to come back to allocation optimization at some point, and even have
some unfinished work removing most allocation from the read path that I'd like
to get back to after accord has shipped.
> Remove test-memory target
> -------------------------
>
> Key: CASSANDRA-17947
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17947
> Project: Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Ekaterina Dimitrova
> Priority: Low
> Fix For: 4.0.x, 4.1.x, 4.x
>
>
> I noticed the {{test-memory}} target which seems to have been added in
> CASSANDRA-15388. Unfortunately, since then _java-allocation-instrumenter_
> which was added as a dependency was not really maintained by the authors. I
> think this is the official repo -
> [https://github.com/google/allocation-instrumenter] and last commit was to
> support Java 8 in 2020. The test itself was also not added to CI.
> Confirmed with [~dcapwell] in Slack
> CC [~bdeggleston] and [~benedict]
--
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
