octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GUI release


From: Daniel J Sebald
Subject: Re: GUI release
Date: Tue, 27 Jan 2015 23:51:44 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16

On 01/27/2015 09:11 PM, Daniel J Sebald wrote:

It seems to me there are two significant time drains: the GUI display
and the atomic reference counts (per your data). And then perhaps there
is a bit for something else--perhaps the workspace variable update...but
I don't see anything happening in the workspace during the following
computation:

GUI:
t0=cputime(); x=1; for i=1:1000000; x = sqrt(x+1); end; t1=cputime();
t1-t0
ans = 9.5256
t0=cputime(); x=1; for i=1:1000000; x = sqrt(x+1); end; t1=cputime();
t1-t0
ans = 9.4986

CLI:
octave:1> t0=cputime(); x=1; for i=1:1000000; x = sqrt(x+1); end;
t1=cputime(); t1-t0
ans = 8.1318
octave:2> t0=cputime(); x=1; for i=1:1000000; x = sqrt(x+1); end;
t1=cputime(); t1-t0
ans = 8.7867

Part of this loss could be due to context switching of the Octave (worker) process and GUI process. Although, my guess would be that the multithreading shouldn't account for more than a percent of two, but I'm not sure.

Dan



reply via email to

[Prev in Thread] Current Thread [Next in Thread]