Derek Gaston

Assigning myself here - I'm going to transition the restart system over to using the MOOSE internal backup capability for the main app (like we do for sub-apps). That will...

Thanks for pointing me to that - I'll use that. That said, is there a reason the branch page can't update too? I could still see people wanting that.

1c31b25 cuts residual computation time in half by simply trying to NOT compute derivatives during residual computation... but I'm sure it's not quite architected right (I'm still not great at...

If you completely turn off derivative calculation (by replacing the two `if()` statements in 1c31b25 with `if(false)`) the residual computation will only be double (7 vs 3.5) when using NumberArray....

BTW: When using NumberArray the amount of storage set aside for derivatives has a HUGE impact on the runtime. 10: 5 seconds 100: 6 seconds 1000: 32 seconds 10000: Too...

That timing was with derivative computation off. Here it is with it on: 10: 5.5 seconds 100: 26 1000: 286

Just trying to get to know the datastructures here... I implemented something called `FriedmudArray` that's backed by a `std::map`... that was an incredible failure (as you might imagine!). It came...

What do you think about my attempts at removing derivative computation ( 1c31b2586ec7486546eb4d11b7c2a1ac980ffe33 )? I have a few more local commits that do even more... but to actually make it...

Yes, yes.... all _true_ computer scientists would say that the thing to do is template this up the wazoo to avoid the derivative computation.... I've gone over this in my...

Just to throw some more blasphemy in here... I'm actually thinking that a global (!) variable like `MetaPhysicL::compute_derivatives` would be useful. I could set it to `true` during Jacobian computation...