Forced data recomputation upon software update?

[sevenless]

I noticed that starting with the version 4.x updates, every time I apply an update the system automatically performs a data recomputation, whereas with the old 3.x versions this did not happen.

Since I'm running on an NSLU2 unit, recomputation takes a very long time and causes most of my uploaded graphs to be out-of-date until the recomputation is completed.

It seems unnecessary to do this unless the structure of the computed data is changing with each patch. Can this be looked into?

[d_l]

I will second this concern for the forced recomputes.

It seems that my average system load on the NSLU2 is gradually increasing with time since I had to make a new USB thumb drive after the original one became corrupted. There hasn't been a significant increase in the data stored on it and no increase in the programmed work load during this time. I believe that an excessively high system load (system load well over 4.0) after upgrading to 4.x versions may have contributed to the corruption.

I fear that a forced recompute at these new higher base loads will push the system loads too high during the recompute and cause corruption of the new USB thumb drive.

Could the gradually increasing system base load be due to some sort of data fragmentation problem on the USB thumb drive?