Next session is on Optimization Practices for the Contract-based APIs #AcumaticaDevSummit pic.twitter.com/hpAm0lf5a1
— Tim Rodman (@TimRodman) June 21, 2018
Nice to see a developer from an Acumatica partner presenting. Just goes to show that the community is growing. #AcumaticaDevSummit pic.twitter.com/fgy52bFL3s
— Tim Rodman (@TimRodman) June 21, 2018
We'll be covering these three main topics #AcumaticaDevSummit pic.twitter.com/nmKkTZbXCA
— Tim Rodman (@TimRodman) June 21, 2018
Some info about ReturnBehavior which is your friend #AcumaticaDevSummit pic.twitter.com/106NP7eZGf
— Tim Rodman (@TimRodman) June 21, 2018
Why you should care about ReturnBehavior (200 hours vs. 3.3 hours), backed up by a fancy scientific formula #AcumaticaDevSummit pic.twitter.com/xV0cb19tFH
— Tim Rodman (@TimRodman) June 21, 2018
Why Generic Inquiries can be your friend too. Hey, that reminds me of this post: https://t.co/xyKrHbK4Jj #AcumaticaDevSummit pic.twitter.com/ZIE76zAtxD
— Tim Rodman (@TimRodman) June 21, 2018
They had a situation where it took over 20 minutes to retrieve records through the base graph but only seconds with a Generic Inquiry. #AcumaticaDevSummit
— Tim Rodman (@TimRodman) June 21, 2018
Now for the meat and potatoes of the presentation: Multi-Threading. Let's start with reasons why you would bother with Multi-Threading. #AcumaticaDevSummit pic.twitter.com/7cUY6JaLKM
— Tim Rodman (@TimRodman) June 21, 2018
Multi-Threading reduced processing time from 5.5 hours to 1 hour for one of their clients #AcumaticaDevSummit
— Tim Rodman (@TimRodman) June 21, 2018
Be careful, the benefits you get from Multi-Threading are not linear, it's more complicated than that. #AcumaticaDevSummit pic.twitter.com/ew0a2AnHl0
— Tim Rodman (@TimRodman) June 21, 2018
Here's a sample configuration for an actual Multi-Threading project #AcumaticaDevSummit pic.twitter.com/AtoUWD3Eee
— Tim Rodman (@TimRodman) June 21, 2018
Some notes about implementing Multi-Threading #AcumaticaDevSummit pic.twitter.com/WxtGYwvB8W
— Tim Rodman (@TimRodman) June 21, 2018
The default number of simultaneous connections is 2 in order to reduce Denial of Service attacks. So you have to modify this. #AcumaticaDevSummit pic.twitter.com/5l922Bt43i
— Tim Rodman (@TimRodman) June 21, 2018
You also have to tweak the Cache settings #AcumaticaDevSummit pic.twitter.com/JX2eDgnFXz
— Tim Rodman (@TimRodman) June 21, 2018
Don't forget to logoff!!!! Use IDisposable for this. iDisposable huh? Sounds like an Apple function. #AcumaticaDevSummit pic.twitter.com/9smrhH8HOL
— Tim Rodman (@TimRodman) June 21, 2018
Each thread can run under the same user #AcumaticaDevSummit
— Tim Rodman (@TimRodman) June 21, 2018
From this you can see that the answer isn't always to keep adding more threads. It's a little more complicated than that. Continuing to add threads can actually negatively impact performance. #AcumaticaDevSummit pic.twitter.com/8ZxAHOlRQh
— Tim Rodman (@TimRodman) June 21, 2018
Josh will also be publishing a blog post with more info about this session, including the code that was shown #AcumaticaDevSummit
— Tim Rodman (@TimRodman) June 21, 2018