SHARE
TWEET

Untitled

a guest Jun 25th, 2019 62 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1.  
  2.  
  3. Ashley Kuritz
  4. ,
  5. 09:15
  6. ,
  7. @Scott Coleman @Bill Riemers
  8. Kelly McGeedy has brought up the latancy issue, and Chandra wants us to look at it closer with her, to see if we can find a solution
  9. She has described the issue happening on 3 different opportunities, at the same area.
  10. I can't give any more details, because that is the extent of what I have been given
  11. I was hoping we could jump on a call with Kelly and have her simulate the issue.
  12.  
  13. Scott Coleman
  14. ,
  15. 09:21
  16. ,
  17. My first availability for a real-time call is 2pm but I know this is important - could Kelly record a Bluejeans video that shows her going through the steps where she has performance issues and share it with us?
  18.  
  19. Ashley Kuritz
  20. ,
  21. 09:22
  22. ,
  23. good Idea, let me talk to her
  24.  
  25. Scott Coleman
  26. ,
  27. 09:22
  28. ,
  29. Edited,
  30. Then I could review this morning possibly between meetings
  31. Just rechecked my calendar and I am now open at 10am today for a live call
  32.  
  33. Bill Riemers
  34. ,
  35. 09:37
  36. ,
  37. Kiran has a configuration update to reduced the latency by about 40%.   That is really the only "quick" fix.  But we have lots of less dramatic improvements we could do that could combine to have a big effect.
  38. We don't really need the problem simulated again...
  39.  
  40. Ashley Kuritz
  41. ,
  42. 09:38
  43. ,
  44. Good news! okay, however, Kelly has thrown this up to Essam who wants us to look at her specific issue, the configuration may help, but to appease them can I still have her record it, or have you seen her specific issue already?
  45.  
  46. Scott Coleman
  47. ,
  48. 09:40
  49. ,
  50. Please have her record it - I don't want to assume we know what this issue is she's seeing
  51.  
  52. Ashley Kuritz
  53. ,
  54. 09:40
  55. ,
  56. okay, thanks 🙂
  57.  
  58. Bill Riemers
  59. ,
  60. 09:42
  61. ,
  62. That seems reasonable to me.
  63.  
  64. Ashley Kuritz
  65. ,
  66. 09:54
  67. ,
  68. They are asking that you guys see it live as well, I added you to the invite, however  she is working on the demo now (recording it)
  69. if  I can just come to the table with we hear you, there's no need to do this live, and this is what we propose, I think that may be a better use of everyone's time.
  70. **Correct me if i am wrong**
  71.  
  72. Scott Coleman
  73. ,
  74. 10:05
  75. ,
  76. I don't see any additional value in seeing it live - I would just be there to capture a recording so I can share the example with anyone else engaged on the performance issues.
  77. I appreciate Kelly stepping up and being willing to reproduce the issue for us
  78.  
  79. Bill Riemers
  80. ,
  81. 10:07
  82. ,
  83. The main value of seeing it live would be if it turns out it isn't what we are expecting, and it isn't an apple to apple comparison, maybe we could suggest better things to look at.  But in that case, I would personally prefer the chance to review and really think through my suggestions first.
  84.  
  85. Ashley Kuritz
  86. ,
  87. 10:10
  88. ,
  89. okay, i hear both of you 🙂 stand by, and as soon as I get it- I will send it your way. You both should have the invite for the 1:30 call, if you can make it that would be great.
  90.  
  91. Bill Riemers
  92. ,
  93. 55 mins
  94. ,
  95. I just forwarded you the both the previous discussions around, what I think is the  same case.
  96.  
  97. Ashley Kuritz
  98. ,
  99. 50 mins
  100. ,
  101. okay, just sent the recordings your way
  102. check your email
  103.  
  104. Scott Coleman
  105. ,
  106. 50 mins
  107. ,
  108. Thanks Ashley!
  109.  
  110. Ashley Kuritz
  111. ,
  112. 49 mins
  113. ,
  114. You're welcome!
  115.  
  116. Scott Coleman
  117. ,
  118. 32 mins
  119. ,
  120. I will continue to say this to whoever will listen - I don't think these are issues we will solve realtime in meetings with users - I think we need to staff a performance initiative to really dive into this
  121. So I wouldn't expect to have any quick fixes at 1:30
  122.  
  123. Bill Riemers
  124. ,
  125. 29 mins
  126. ,
  127. Just looked.  Indeed this is the same as the case I forwarded.  Only this is the renewal scenario.  Our slowest case for renewals is many public sector, many lines, where incentives apply...
  128.  
  129. Bill Riemers
  130. ,
  131. 26 mins
  132. ,
  133. So with batch size update we would drop this from 3:20 to about 2:10.   A second think we can do for this worst case scenario is rewrite the target discount flow.  But that only impacts the very initial cart load.  It could potentially reduce that time by an additional 40%.
  134.  
  135. Ashley Kuritz
  136. ,
  137. 25 mins
  138. ,
  139. okay, the batch size update-- is that what Kiran has created? or is that somethihng different
  140.  
  141. Bill Riemers
  142. ,
  143. 24 mins
  144. ,
  145. Yes.  Kiran has the batch size update ready, and that is what we tested in our e-mail.   We really just need the green light to activate that in production, as it is a single configuration variable update.
  146.  
  147. Ashley Kuritz
  148. ,
  149. 24 mins
  150. ,
  151. understood
  152. that still doesn't really get us where we need, it's improvement. But Chandra is wanting this done in seconds, not minutes.
  153.  
  154. Bill Riemers
  155. ,
  156. 22 mins
  157. ,
  158. The flow update we haven't worked on, because it would need to be a story.  Basically what happens today is when we apply the target discount for a renewal incentive, we reprice again.   In theory we have all the data we need just to calculate the prices.   Only we didn't do it that way because we felt more confident allowing Apttus to do the calculations.   But it might speed up the initial cart load significantly to take the more complicated approach of recalculating the prices without relying on Apttus to do it.
  159.  
  160. Ashley Kuritz
  161. ,
  162. 21 mins
  163. ,
  164. I agree with Scott's approach that with this performance issue we need to look at potentially creating a "mini" project team to look at this, and create + Complete.
  165.  
  166. Scott Coleman
  167. ,
  168. 20 mins
  169. ,
  170. Devote some people to this full time, free them of their other responsibilities, these are actions that would make this a clear top priority. Right now it seems like we're trying to rely on people's spare cycles to solve this. I don't think that will be successful
  171.  
  172. Bill Riemers
  173. ,
  174. 20 mins
  175. ,
  176. Yeah.  That is the problem.  It is impossible for any of us to work on this without dropping something else on the floor...
  177.  
  178. Ashley Kuritz
  179. ,
  180. 20 mins
  181. ,
  182. okay
  183. let me bring that up to Chandra
  184.  
  185. Scott Coleman
  186. ,
  187. 20 mins
  188. ,
  189. Bold reprioritization is needed
  190.  
  191. Ashley Kuritz
  192. ,
  193. 19 mins
  194. ,
  195. indeed. We will never get this right unless we pivot.
  196.  
  197. Bill Riemers
  198. ,
  199. 19 mins
  200. ,
  201. We have plenty of data to identify issues.   For example, everytime I price a scenario like these I see the following in my e-mail:
  202. ApexApplication <info@salesforce.com>
  203. Mon, Jun 24, 3:22 PM (19 hours ago)
  204. to briemers+stage@redhat.com
  205.  
  206. Operation: /apexremote
  207.  
  208. By user/organization: 00560000000mStZ/00D190000009U62
  209.  
  210. Caused the following Apex resource warnings:
  211.  
  212. Apttus_Config2:Number of query rows: 33030 out of 50000
  213.  
  214. (these emails can be disabled from the user detail page for this user)
  215.  
  216. Operation: /apexremote
  217.  
  218. By user/organization: 00560000000mStZ/00D190000009U62
  219.  
  220. Caused the following Apex resource warnings:
  221.  
  222. Apttus_Config2:Number of SOQL queries: 54 out of 100
  223.  
  224. (these emails can be disabled from the user detail page for this user)
  225. These type of messages tell us we have way too much processing going on while pricing...
  226. But it takes a lot of analysis and hard work to determine from that what we can actually work on.
  227.  
  228. Scott Coleman
  229. ,
  230. 18 mins
  231. ,
  232. I can join the call with Kelly and Essam at 1:45
  233.  
  234. Ashley Kuritz
  235. ,
  236. 18 mins
  237. ,
  238. okay, good.
  239. I see what you are saying Bill
  240. For a team what resources would we need?
  241.  
  242. Bill Riemers
  243. ,
  244. 17 mins
  245. ,
  246. But we also need to set realistic scenarios.  If you have dozens of lines in the cart, we probably won't get the time below 1 minute, even if we strip out all our custom logic.
  247.  
  248. Ashley Kuritz
  249. ,
  250. 17 mins
  251. ,
  252. 1 tech, 1 BSA?
  253.  
  254. Bill Riemers
  255. ,
  256. 16 mins
  257. ,
  258. tech, BSA, QASource, Product Owner.  I think that is a minimum team.
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!
 
Top