[ 
https://issues.apache.org/jira/browse/OAK-11182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17924045#comment-17924045
 ] 

Horia Poradici edited comment on OAK-11182 at 2/5/25 12:35 PM:
---------------------------------------------------------------

Usage example for tool for creating EMPTY_PROPERTIES garbage:

java -jar /oak-run.jar create-test-garbage "$(get_mongo_uri)" create 
--garbageNodesCount 5 --garbageType 1 --garbageNodesParentCount 1 
--generateGarbageBatchDelaySeconds 1


was (Author: JIRAUSER305838):
Usage example for tool for creating garbage:

java -jar /oak-run.jar create-test-garbage "$(get_mongo_uri)" create 
--garbageNodesCount 5 --garbageType 1 --garbageNodesParentCount 1 
--generateGarbageBatchDelaySeconds 1

> Create and test general mechanism for creating MongoDocumentStore fullGC 
> garbage for testing
> --------------------------------------------------------------------------------------------
>
>                 Key: OAK-11182
>                 URL: https://issues.apache.org/jira/browse/OAK-11182
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: mongomk
>            Reporter: Horia Poradici
>            Assignee: Rishabh Daim
>            Priority: Major
>             Fix For: 1.74.0
>
>
> The purpose of this ticket is to create methods for generating garbage that 
> can be collected as part of testing fullGC.
> A new Command class in oak-run should be used for this, with parameters for 
> adjusting how garbage should be generated.
> The methods used in VersionGarbageCollectorIT.java for generating garbage can 
> be used as inspiration and/or starting point.
> The usage of these methods will be to run them on the MongoDB of the stage 
> environment that we are currently testing on, and to check how fullGC 
> continuously collecting the garbage affects performance of the Author pods.
>  
> *Definition of Done:*
> Methods are created for doing the following:
> 1. Generate *1.000+* fullGC garbage (of type EMPTY_PROPERTIES) under a 
> *single* node.
> 2. Generate *10.000+* fullGC garbage (of type GAP_ORPHANS or 
> EMPTY_PROPERTIES) under *multiple* nodes.
> 3. Generate *50.000+* fullGC garbage of type GAP_ORPHANS (in total) under 
> *1.000+* nodes.
> 4. Generate *200.000+* fullGC garbage of type GAP_ORPHANS (in total) under 
> *10.000+* nodes.
> The methods should allow for generation of garbage on {*}any MongoDB 
> database{*}, specified by connection string.
> The methods should be as general as possible, with parameters for the number 
> of: 
>  * total fullGC garbage nodes to create
>  * the total number of nodes under which to create garbage
>  * the type of garbage to create: at least EMPTY_PROPERTIES and GAP_ORPHANS 
> should be supported, with the possibility of adding more in the future.
>  * *delays* for generating garbage repeatedly, as well as {*}number of 
> repeated runs{*}, so the method can be started and it should run for an 
> indefinite period of time
>  * the *modified* timestamp for the created nodes, so that garbage with any 
> *age* can be generated



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to