wonder if it has to do with rebuilding SS indexes ...
# suitescript
a
wonder if it has to do with rebuilding SS indexes @francis? i haven't noticed anything directly but that may explain some issues i'm seeing
f
I experienced it with Map/Reduce, but there is some third party routines that I believe to be running on SS and they are taking a lot more time to conclude, but those are wrap in a Suitelet, so I am not 100% sure what runs on the back
My MapReduce went from 4 hours (1 single thread) to 7 hours (same one single thread) from before the update to after the update
a
hmm, yeah could be many things
f
Same amount of data being processed
k
You have to choose the level of parallelism when you deploy the script.
f
But it seems to only be on Thread scripts, I checked the performance analysis for the rest of the Scripts and they are almost the same from before
@Kevin I am aware of that, but I choose to run it with one Thread in both test to check my theory