CASSANDRA-18131 Fix LongBTreeTest test timeout

[Mmuzaf]

Thanks for sending a pull request! Here are some tips if you're new here:

• Ensure you have added or run the appropriate tests for your PR.
• Be sure to keep the PR description updated to reflect all changes.
• Write your PR title to summarize what this PR proposes.
• If possible, provide a concise example to reproduce the issue for a faster review.
• Read our contributor guidelines
• If you're making a documentation change, see our guide to documentation contribution

Commit messages should follow the following format:

<One sentence description, usually Jira title or CHANGES.txt summary>

<Optional lengthier description (context on patch)>

patch by <Authors>; reviewed by <Reviewers> for CASSANDRA-#####

Co-authored-by: Name1 <email1>
Co-authored-by: Name2 <email2>

The Cassandra Jira

[michaelsembwever]

the default value of this tests parameter is perThreadTrees * threads, so we could be replacing values of 1000 with 25600 (where there are 32 availableProcessors). Note in ant we limit this to 2 processors here so a value of 1600 (which is still an increase).

is this what you intended @Mmuzaf ?

[Mmuzaf]

Correct, I think we can safely increase the number of local runs for testLargeBatchesLargeRange, and testIndividualInsertsMediumSparseRange while still maintaining a reasonable execution time for the LongBTreeTest as a whole.

For the tests that fire testInsertions with parameters the main concern we have is - we perform different numbers of test attempts to check tree insertions for variations of ranges and batches, but the same equal number of tests should be used for all of them. I think perThreadTrees * threads is the better choice for us since increasing the perThreadTrees (for testInsertions it's not exactly trees per thread as it says, it's just a multiplier) will give us the ability to find patterns e.g. for a heap consumption during a particular run.

[Mmuzaf]

It is also possible to just set the perThreadTrees for 10000 back to 100 as an easy fix, I guess. I just wanted to fix the problem wider and maybe I overdid it :-)