Here is a summary of B1 data posted on SF drives. There is not enough info on what happened with Vapor’s SF drive. Vapor also did a lot of testing on compression before getting started on the endurance app, which would have made a difference; plus it has modified f/w.
Anyway, when the endurance app is running all the time B1 appears to only increase. I’m wondering if SynbiosVyse’s drive failed due the fact that B1 got too high. The difference between least and most worn blocks exceeds the P/E cycle capability.
130 = (6,500 / 5,000] x 100
130 = (3,900 / 3,000] x 100
Edit: Looking at SynbiosVyse’s posts he mentions he had hardly any static data (a few MB?) yet B1 was still able to significantly increase above the target SF value.
![]()




Reply With Quote

Bookmarks