Jira (PDB-470) Investigate setStatementsCacheSize for performance

[Kenneth Barber (JIRA)]

Title: Message Title

Kenneth Barber commented on an issue   Re: Investigate setStatementsCacheSize for performance Find attached a couple of screenshots for before/after patch results. Like I said, I've tried this 3 times and found similar results each time, so I'm sure its not by accident. This appears to be a simple facility that provides hashes lookups of previously prepared statements so they can be re-used. Without this, prepared statements are being prepared then destroyed after a single use. By using prepared statements we avoid a hard-parse in postgresql and with multiple use Postgresql can avoid plan calculation after a while once it considers a plan stable. So big performance benefits it would seem. The alternative is to look at doing our own prepared statements. Add Comment   PuppetDB / PDB-470 Investigate setStatementsCacheSize for performance It seems the setting setStatementsCacheSize for BoneCPConfig will enable prepared statements cache. This seems to have a great effect on our insert time, especially at high load. So far I've tested this 3 times and found that the number of seconds spent doing inserts is almost halved. The patch I was working with is here: {code} --- a/src/com... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.