[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Should xelem bounds-check (and reference-check) when debugging optio
From: |
Carnë Draug |
Subject: |
Re: Should xelem bounds-check (and reference-check) when debugging options are on |
Date: |
Wed, 25 Jun 2014 02:38:23 +0100 |
On 25 June 2014 02:18, Dmitri A. Sergatskov <address@hidden> wrote:
> On Tue, Jun 24, 2014 at 6:59 PM, Rik <address@hidden> wrote:
>>
>> On 06/24/2014 04:44 PM, David Spies wrote:
>>
>>
>>
>>> 6/24/14
>>>
>>> David,
>>>
>>> Since there have been a bunch of threads recently on Octave performance,
>>> could you benchmark this change to see if there are any performance
>>> issues
>>> in the ordinary case where BOUNDS_CHECKING is disabled?
>>>
>> As jwe pointed out, asserts are always enabled in Octave, so I need to
>> know how to add a new flag telling Octave whether to reference-check. Once
>> I've done that, I'd be happy to benchmark the result. Is there a standard
>> set of Octave benchmarks I can use?
>>
>> David,
>>
>> We don't have a formal performance benchmark. But, we often use 'time
>> make check' from the shell. This should be good enough to know whether we
>> should be concerned or not.
>>
>> --Rik
>
>
> It used to be an octave-forge package "benchmark" which has been moved to
> "unmaintained" and I do
> not even now how to get it. I still have a copy of benchmark-1.1.1 tarball
> which I can send if anyone is
> interested. It is just a few m-files and they are all seem to work with
> 3.8.1...
It's still available from Octave Forge [1]. It has its own hg repo [2]
if anyone wishes to continue it.
Carnë
[1]
http://sourceforge.net/projects/octave/files/Octave%20Forge%20Packages/R2009-05-08/benchmark-1.1.1.tar.gz
[2] https://sourceforge.net/p/octave/benchmark/ci/default/tree/