Optimizing your Logik Configuration Series<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #7057C7; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Your company purchased and is implementing Logik.io because you want to sell more, sell faster, and maintain less with guided, intuitive, always fast configuration experiences in CPQ. Logik gives you the tools to build a fast configuration. But at the end of the day, the performance of your configuration depends on how you build it. Imagine someone is running a marathon (26.2 miles (42.2 km for our non US customers). At the end of mile 1, the runner realizes her shoe is untied and takes 5 seconds and ties the shoe. A 5 second delay on a race that takes 2-6 hours is not a big deal. But now imagine the runner did a bad job tying the shoe, and has to tie her shoes every mile. Now we are up to 130 seconds- which has added over 2 minutes to her time! And that is just time lost for laces- you can see the time starts to add up when you add in bathroom breaks, water stations, first aid…. Etc. And just like our runner, we want to minimize unnecessary trivial delays that could stack up and slow us down. That is what this series of articles looks at. Table Queries - How to reduce the number of queries needed during configuration