[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 20 GB console.log documents generated
From: |
Henry F. Mollet |
Subject: |
Re: 20 GB console.log documents generated |
Date: |
Tue, 30 Oct 2007 13:31:52 -0700 |
User-agent: |
Microsoft-Entourage/11.1.0.040913 |
On OS X 10.4.9 with 1.42 GHz PowerPC G4:
octave-2.9.15:13> tic
octave-2.9.15:14> T = 0 : 0.0001 : 2 - .0001;
octave-2.9.15:15> Y = 2.3*sin(2*pi*10*T);
octave-2.9.15:16> toc
Elapsed time is 0.177666 seconds.
octave-2.9.15:17> plot(T,Y)
octave-2.9.15:18> toc
Elapsed time is 2.765343 seconds.
These results are similar to those given by Dimitry and JWE and imply that
PPC does not choke on this.
Henry
on 10/30/07 11:00 AM, John W. Eaton at address@hidden wrote:
> On 30-Oct-2007, Dmitri A. Sergatskov wrote:
>
> | I am not Cal, but I do not understand since when 20000 points becomes
> | "too many."
> | I am routinely plot 10 times as much. I would like to have a rough idea what
> | my data look like before start messing with it. BTW on my computer the
> | Cal's code returns:
> |
> |
> | octave:1> tic
> | octave:2>
> | octave:2> T = 0 : 0.0001 : 2 - .0001;
> | octave:3> Y = 2.3*sin(2*pi*10*T);
> | octave:4>
> | octave:4> toc
> | Elapsed time is 0.129105 seconds.
> | octave:5>
> | octave:5> plot(T,Y)
> | octave:6>
> | octave:6> toc
> | Elapsed time is 1.222946 seconds.
> | octave:7> whos Y
> |
> | *** local user variables:
> |
> | Prot Name Size Bytes Class
> | ==== ==== ==== ===== =====
> | rwd Y 1x20000 160000 double
> |
> | Total is 20000 elements using 160000 bytes
> |
> | octave:8>
> |
> | Of course, after the last "toc" gnuplot takes some (very short) time
> | to plot the data octave handed to it. This is with octave-2.9.9 on
> | Fedora 7, so octave still writes the temp data file (0.5M).
>
> On my system it took around two seconds to do this. So there may be
> some penalty for sending the data in a pipe to gnuplot, but it should
> still work.
>
> | In any case, if PPC version chocks on this, there is something
> | really, really wrong with that setup...
>
> Defnitely. But I don't think it is Octave's fault. As I think I said
> before, Octave does not directly write to any file called
> console.log. That sounds like it might be some history thing created
> by the terminal application in which Octave is running. I think
> someone more familiar with OS X (I think it was OS X) will have to
> comment.
>
> jwe
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://www.cae.wisc.edu/mailman/listinfo/help-octave
- 20 GB console.log documents generated, Cal, 2007/10/29
- Re: 20 GB console.log documents generated, Jordi GutiƩrrez Hermoso, 2007/10/29
- Re: 20 GB console.log documents generated, Cal, 2007/10/29
- Re: 20 GB console.log documents generated, Jordi GutiƩrrez Hermoso, 2007/10/29
- Re: 20 GB console.log documents generated, cal, 2007/10/30
- Re: 20 GB console.log documents generated, James Sherman Jr., 2007/10/30
- Re: 20 GB console.log documents generated, Dmitri A. Sergatskov, 2007/10/30
- Re: 20 GB console.log documents generated, John W. Eaton, 2007/10/30
- Re: 20 GB console.log documents generated,
Henry F. Mollet <=