On Tue, 4 Mar 2025 17:20:28 GMT, Thomas Schatzl wrote:
>> Hi all,
>>
>> please review this change that implements (currently Draft) JEP: G1:
>> Improve Application Throughput with a More Efficient Write-Barrier.
>>
>> The reason for posting this early is that this is a large change, and the
On Wed, 5 Mar 2025 09:45:00 GMT, Thomas Schatzl wrote:
>> Hi all,
>>
>> please review this change that implements (currently Draft) JEP: G1:
>> Improve Application Throughput with a More Efficient Write-Barrier.
>>
>> The reason for posting this early is that this is a large change, and the
On Tue, 4 Mar 2025 09:57:56 GMT, Thomas Schatzl wrote:
>> Hi all,
>>
>> please review this change that implements (currently Draft) JEP: G1:
>> Improve Application Throughput with a More Efficient Write-Barrier.
>>
>> The reason for posting this early is that this is a large change, and the
On Tue, 4 Mar 2025 08:26:10 GMT, Thomas Schatzl wrote:
>> src/hotspot/share/gc/g1/g1CollectionSet.cpp line 310:
>>
>>> 308: verify_young_cset_indices();
>>> 309:
>>> 310: size_t card_rs_length =
>>> _policy->analytics()->predict_card_rs_length(in_young_only_phase);
>>
>> Why are we using
On Tue, 4 Mar 2025 08:36:58 GMT, Thomas Schatzl wrote:
>> `cards_still_refer_to_cset` refers to cards that were found to have already
>> been marked as `to-collection-set`. Renamed to
>> `_cards_already_refer_to_cset`, would that be okay?
>
> Fwiw, this particular counter is just for statistics
On Mon, 3 Mar 2025 08:42:05 GMT, Thomas Schatzl wrote:
>> Hi all,
>>
>> please review this change that implements (currently Draft) JEP: G1:
>> Improve Application Throughput with a More Efficient Write-Barrier.
>>
>> The reason for posting this early is that this is a large change, and the
