Do you guys get the same ‘for loop’ performance in MXS 2017 and previous versions?
(
st = timestamp()
for j = 1 to 1000000 do ()
format "time:%
" (timestamp()-st)
)
2009: 213
2010: 236
2011: 314
2012: 324
2013: 262
2014: 281
2015: 298
2016: 254
2017: 547
could you provide the prices per version as well?
we could estimate the max in $ per ms?
Max 2016: time:311
Max 2017: time:581
Max 2016: time:344
Max 2017: time:667
Max2016: time:177
Max2017: time:353
curious about your machine specs, mine is a i7-4930K @ 4.3GHz
max version:19000 time:398 (max 2017)
max version:16000 time:227 (max 2014)
I hope max team fix this and many problem on maxscript editor on next update.
Thank you so much guys. That’s explains why everything is sooo slow in 2017.
I get pretty much the same results.
Max 2016 time:208
Max 2017 time:419
Well, it wouldn’t be Max is we wouldn’t get a few of these thigs. Perhaps they complied the ‘debug’ version?
Hope it gets fixed soon (if it can be fixed).
there is a new MXSCallstackCaptureEnabled context which can be turned off. Running the loop with this context off, doesn’t help much, but in general this is a hint that some work has happened in the stack unwinding code. And i speculate that the scope entering/exiting in the loop body is affected by this …
Yes, I tried it before posting, but didnt notice any difference.
But, even if it would be the responsible of the slowdown, I couldn’t find a global switch (at least) to turn it off, meaning that you would need to run all your code within this context. I don’t think that is anything good, moreover if you have to modify all your previous code to work that way.
Performance of MXS was never too good, but I can’t think of any good reason that justify slow down the loops by 50%. It’s not a few milliseconds slower, it is literally half the speed.
Of course i do not argue about this being a serious slowdown – just posting about a suspicion
Best way to get this things fixed is to report it ASAP – so please do so…
I can do the same…
And please post the public defect report number after reporting, this helps pushing such issues …
I just came across this thread after finding my scripts running slower in 2017… has there been any more news from the devs on whether this will be fixed in any future service packs?
I’m sure I’m not going out on a limb to suggest this is a bit of a deal-breaker for many studios?