What benefit does running a database with the No Crash Protection (-i) provide?

What benefit does running a database with the No Crash Protection Startup Parameter (-i) provide?
How to run a Progress database with No Integrity?
Can Before Image bi-writes be prevented?
What are the risks of running with No Crash Protection?
Should AI be disabled before accessing the database with the -i (no-integrity) flag?

Running a database with the -i startup parameter causes fewer data and before-image blocks to be written to disk. Running with No Crash Protection (no-integrity) makes I/O intensive operations run much faster, such as binary load operations. This is because when running with the -i (no-integrity) startup flag (-i forces -R) - Buffered Synchronous I/O (O_RDWR) to the bi file and no bi/data order synchronization occurs. For further discussion refer to Article  Does Progress use Synchronous or Asynchronous I/O?   

This means that if the database were to crash or a user get killed even if the system were not to crash as a result, there is no guarantee that crash recovery will complete. In this case, we don't even try to recover, the database is inaccessible:
No Crash Protection (-i) should never be used unless a valid/complete backup exists. Should the database crash while running with No Crash Protection, the database will not be able to go through crash recovery. The only recourse when this happens is to revert to backup. Refer to Article  Database errors 509 and 510 after abnormal shutdown using no crash protection (-i) parameter  

The no-integrity (-i) option should not be used with a database that has AI enabled. Refer to Article  No integrity and AI files   

Understanding the risks, performance is vastly improved running with no integrity (-i) and should be used for distinct I/O intensive operations. For example:

• A binary load process generates high I/O activity on the before-image file (.bi). Performance can be improved by increasing the bi cluster and bi block size to improve fast checkpointing and in addition load with the no-integrity parameter. Refer to Article  Using -i (no integrity) for binary load     
• During LOB data loads - Creating a LOB uses the record subsystem with intensive writes to the bi subsystem. Refer to Article  How to improve the time required to copy/move LOBs between databases  
• Massive delete operations benefit from no integrity, although there are better options. Refer to Article   What is the fastest way to remove all records from a database table?