[Users] CST stage has become slower

[Steven R. Brandt]

I can introduce a flag to disable the training wheels. I'll try and do 
it when I get back.

--Steve


On 02/16/2017 11:04 PM, Frank Loeffler wrote:
> On Thu, Feb 16, 2017 at 04:34:35PM -0600, Roland Haas wrote:
>> I asked the same question and (par for the answer is): it is at parsing
>> it with both methods and then comparing so it must be strictly
>> slower :) This also qualifies for "debug code" I guess.
>
> The idea is to catch cases where the new parser gets to a different 
> result than the old, especially for thorns we don't have access to. I 
> wouldn't call it 'debugging', since there is nothing to debug at the 
> moement, maybe verification - but that is just a name anyway.
>
> The more interesting question is: how much slower did it get for 
> individual users - and was it piraha or something else? It shouldn't 
> be much more than twice as slow, because otherwise it would mean 
> piraha would be slower than the old method. It would still be better 
> than the old method, and it was never meant as a replacement for 
> efficiency reasons, but it would be interesting to know what the 
> difference is.
>
> Steve (I know you are out of town, but at some point you are going to 
> read this): is there an easy way to temporarily disable one or the 
> other method, so that a speed-test could be made by anyone, on their 
> system, with their thorns?
>
> Frank
>
>
>
> _______________________________________________
> Users mailing list
> Users at einsteintoolkit.org
> http://lists.einsteintoolkit.org/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.einsteintoolkit.org/pipermail/users/attachments/20170217/5f8bc728/attachment.html