|
From: | Nicholas Jankowski |
Subject: | [Octave-bug-tracker] [bug #35400] Performance of in-place operations |
Date: | Tue, 30 Nov 2021 15:33:45 -0500 (EST) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36 |
Follow-up Comment #4, bug #35400 (project octave): Octave 6.4.0 on windows, the results I'm seeing from Rik's test script: x = x + 1; Elapsed time is 0.91841 seconds. x++; Elapsed time is 0.602464 seconds. x += 1; Elapsed time is 0.769149 seconds. relative timing: Rik's c#0 Hartmut's c#2 mine x+1 100% 100% 100% x++ 106% 43% 66% x+= 141% 44% 84% so... it seems the in-place operations have consistently improved since this was opened in 2012. should this remain open? should it at least be retitled to indicate the problem is now the x=x+1 performance penalty? (is that a problem? should we expect the interpreter to be able to recognize those two operators and optimize it?) _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?35400> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |