Jira (PDB-5004) Test fully realized sync summary query memory usage

0 views
Skip to first unread message

Zachary Kent (Jira)

unread,
Jan 27, 2021, 1:02:02 PM1/27/21
to puppe...@googlegroups.com
Zachary Kent created an issue
 
PuppetDB / Task PDB-5004
Test fully realized sync summary query memory usage
Issue Type: Task Task
Assignee: Unassigned
Created: 2021/01/27 10:01 AM
Priority: Normal Normal
Reporter: Zachary Kent

We should A/B test the memory usage of fully realizing the sync summary queries vs. using the lazy approach using the SLV data. This should give us a rough indication of the increase in heap usage we can expect with this change. 

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Zachary Kent (Jira)

unread,
Jan 27, 2021, 1:02:04 PM1/27/21
to puppe...@googlegroups.com

Zachary Kent (Jira)

unread,
Jan 27, 2021, 2:21:03 PM1/27/21
to puppe...@googlegroups.com

Zachary Kent (Jira)

unread,
Feb 1, 2021, 12:28:03 PM2/1/21
to puppe...@googlegroups.com

Zachary Kent (Jira)

unread,
Feb 10, 2021, 2:14:02 PM2/10/21
to puppe...@googlegroups.com
Zachary Kent updated an issue
Change By: Zachary Kent
Sprint: HA 2021-02-10 , HA 2020-02-24

Zachary Kent (Jira)

unread,
Feb 16, 2021, 1:54:04 PM2/16/21
to puppe...@googlegroups.com
Zachary Kent commented on Task PDB-5004
 
Re: Test fully realized sync summary query memory usage

I tested this using benchmark data in order to simulate more nodes for the sync summary query. The SLV data has a more realistic dataset but is only for 600 nodes, iirc. The data for the summary query should be similar enough between the two sources because it only pulls certname, timestamp, and entity hash. 

Using benchmark I had two PDBs loaded with 5000 simulated nodes running locally and syncing with one another. One PDB was running the lazy version of the sync code which holds open summary query transactions while it's submitting the the data it needs to transfer into its queue. The other PDB was running the new non-lazy version which realizes the entire summary query in memory and avoids holding open a transaction while records are transferred. I looked at the memory usage using VisualVM over multiple sync runs and was unable to notice any real difference in the overall heap usage between the two approaches. 

 

 

Zachary Kent (Jira)

unread,
Feb 24, 2021, 1:58:02 PM2/24/21
to puppe...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages