Re: [DISCUSS] CASSSIDECAR-254 - Enabling sidecar to collect async profiles

Supportive of inclusion as well. General preference for invoking as a library rather than forking processes. Jon, thanks for the tips on off-CPU profiling - added to my personal cheat sheet. I have seen cases where specific async-profiler/JVM/Cassandra version combos (JDK11/4.1-derived source

RE: [DISCUSS] CEP-49: Hardware-accelerated compression

Thank you, Scott and everyone for all the feedback you have given me. Answering Scott’s questions, – The CEP includes a section labeled "Setup used to generate results above", but I don't see a summary of results, graphs, or benchmark details. Could you point me to them or upload to the Conflue

Re: [DISCUSS] CASSSIDECAR-254 - Enabling sidecar to collect async profiles

Thanks for bringing this discussion Doug. I didn't realize that async-profiler allows you to bring it as a dependency. It looks pretty neat from what I could tell. I also think bringing this to Cassandra as a dependency is a reasonable approach. We need to come up with a solid way to expose this

Re: Question: are committers binding on CEP votes or just PMC members?

Chiming in after being notified of the change to the wiki. We accounted for all this at the time, even for release votes. Note the phrasing: "Discussion / binding votes on releases (Consensus: min 3 PMC +1, no -1)" That is, only positive votes from PMC members are counted, but negative committe

Re: [DISCUSS] CASSSIDECAR-254 - Enabling sidecar to collect async profiles

The nice thing from what I can tell about using the Java API per [6] below is that you can literally just get an instance of the profiler and pass it some commands in the `execute` method… just need to be careful how much of that surface area we expose. Jon (and others obviously) I’d love to get

Re: Question: are committers binding on CEP votes or just PMC members?

At least 3 PMC member votes are required for release ( https://www.apache.org/foundation/voting.html ) due to foundation policy, but if a committer votes against a release the PMC better be paying attention. Would argue it should be commit-bit binding for CEPs, though I’d be shocked if there’s

Re: [DISCUSS] CASSSIDECAR-254 - Enabling sidecar to collect async profiles

> The fact o3 used "Bus-factor" as a dimension is just amazing. Yeah - that got me too. On Fri, Jun 13, 2025, at 2:38 PM, Jon Haddad wrote: > I'd be very happy to see async-profiler included with C* I've made extensive > use of it in my performance evaluations [1][2], and even posted a video ab

Question: are committers binding on CEP votes or just PMC members?

Doug had a great question that had me digging through gdoc comments from 5 years ago to try and figure out the answer. Our governance page here: https://cwiki.apache.org/confluence/display/CASSANDRA/Cassandra+Project+Governance Felt kind of unclear on what committer votes were binding for or no

Re: [VOTE] Clarifying our JDK Support Policy

+1 (nb) with the clarified verbiage (thanks for talking through that with me). Doug > On Jun 13, 2025, at 3:55 PM, Aaron wrote: > > +1 > > On Fri, Jun 13, 2025 at 2:33 PM Yifan Cai > wrote: >> +1 (nb) >> Read through the long discussion, the plan makes sense to me.

Re: [VOTE] Clarifying our JDK Support Policy

+1 On Fri, Jun 13, 2025 at 2:33 PM Yifan Cai wrote: > +1 (nb) > Read through the long discussion, the plan makes sense to me. > > -- > *From:* Brandon Williams > *Sent:* Friday, June 13, 2025 12:09:35 PM > *To:* dev@cassandra.apache.org > *Subject:* Re: [VOTE] Clari

Re: [VOTE] Clarifying our JDK Support Policy

+1 (nb) Read through the long discussion, the plan makes sense to me. From: Brandon Williams Sent: Friday, June 13, 2025 12:09:35 PM To: dev@cassandra.apache.org Subject: Re: [VOTE] Clarifying our JDK Support Policy +1 Kind Regards, Brandon On Fri, Jun 13, 202

Re: [VOTE] Clarifying our JDK Support Policy

+1 On Fri, 13 Jun 2025 at 15:10, Brandon Williams wrote: > +1 > > Kind Regards, > Brandon > > On Fri, Jun 13, 2025 at 12:23 PM Josh McKenzie > wrote: > > > > If removed, we drop the required older JDK across all branches when the > feature is removed. > > > > Talking to Doug about this; let's r

Re: [VOTE] Clarifying our JDK Support Policy

+1 Kind Regards, Brandon On Fri, Jun 13, 2025 at 12:23 PM Josh McKenzie wrote: > > If removed, we drop the required older JDK across all branches when the > feature is removed. > > Talking to Doug about this; let's revise this phrasing to: > "When the feature has been removed from all supported

Re: [VOTE] Clarifying our JDK Support Policy

+1 On Jun 13, 2025 at 12:22:06 PM, Josh McKenzie wrote: > If removed, we drop the required older JDK across all branches when the > feature is removed. > > Talking to Doug about this; let's revise this phrasing to: > "When the feature has been removed from all supported branches, the > constrai

Re: [VOTE] Clarifying our JDK Support Policy

+1 On Fri, Jun 13, 2025 at 11:40 AM Mick Semb Wever wrote: > +1 > > On Fri, 13 Jun 2025 at 13:58, Josh McKenzie wrote: > >> +1 >> >> On Fri, Jun 13, 2025, at 7:56 AM, Josh McKenzie wrote: >> >> [DISCUSS] thread: >> https://lists.apache.org/thread/vr7j2ob92k6fbcwvlfo60l3scylzdbft >> >> Text to v

Re: [DISCUSS] CASSSIDECAR-254 - Enabling sidecar to collect async profiles

I'd be very happy to see async-profiler included with C* I've made extensive use of it in my performance evaluations [1][2], and even posted a video about it [3] for general Java perf analysis (among others). It's part of easy-cass-lab and is easily the most informative tool I've found for the ge

Re: [VOTE] Clarifying our JDK Support Policy

+1 On Fri, 13 Jun 2025 at 13:58, Josh McKenzie wrote: > +1 > > On Fri, Jun 13, 2025, at 7:56 AM, Josh McKenzie wrote: > > [DISCUSS] thread: > https://lists.apache.org/thread/vr7j2ob92k6fbcwvlfo60l3scylzdbft > > Text to vote on: > >

Re: [VOTE] Clarifying our JDK Support Policy

> If removed, we drop the required older JDK across all branches when the > feature is removed. Talking to Doug about this; let's revise this phrasing to: "When the feature has been removed from all supported branches, the constraint to retain JDK support for that feature drops with it." On Fri

Re: [DISCUSS] CASSSIDECAR-254 - Enabling sidecar to collect async profiles

The fact o3 used "Bus-factor" as a dimension is just amazing. After reading more about the project, the possibilities are pretty interesting. I suspect we'll see this in a Haddad talk soon. On Fri, Jun 13, 2025 at 1:57 AM Josh McKenzie wrote: > I was curious if o3 (model from OpenAI) would be a

Re: [VOTE] Clarifying our JDK Support Policy

+1 On Fri, Jun 13, 2025, at 7:56 AM, Josh McKenzie wrote: > [DISCUSS] thread: > https://lists.apache.org/thread/vr7j2ob92k6fbcwvlfo60l3scylzdbft > > Text to vote on: > -- > *[New LTS JDK Adoption]* > • When a ne

[VOTE] Clarifying our JDK Support Policy

[DISCUSS] thread: https://lists.apache.org/thread/vr7j2ob92k6fbcwvlfo60l3scylzdbft Text to vote on: -- *[New LTS JDK Adoption]* • When a new JDK goes LTS, we prioritize: • Moving trunk to build, run, pass CI,

Re: [DISCUSS] CASSSIDECAR-254 - Enabling sidecar to collect async profiles

I was curious if o3 (model from OpenAI) would be able to do a deep dive health check on a repo to assist in considering taking it as a dependency. The results can be found here: https://chatgpt.com/share/684be703-1d4c-8002-b831-f997f829f4b4 Apparently it can, and can do it quite well. This was