Persistent messages are written to disk and hence, may be recovered if the message broker crashes for some reason.
持久性消息会写入磁盘，因此如果消息代理因为某种原因发生崩溃，则可以恢复这些消息。
Persistent messages are written to disk and are therefore recoverable in the event of a system failure, but are correspondingly slow.
持久化的消息则会把消息写入磁盘，即便系统发生故障也可找回消息，但相应的处理速度较慢。
Sending a persistent message outside of a transaction, or committing after every message, can lead to delays due to disk access.
将持久性消息发送到事务之外，或者在每条消息之后提交，都可能由于磁盘访问而导致延迟。
Persistent preallocation If an application needs to allocate disk space before actually using it, most file systems do so by writing 0s to the not-yet-used disk space.
持久性预分配如果一个应用程序需要在实际使用磁盘空间之前对它进行分配，大部分文件系统都是通过向未使用的磁盘空间写入0来实现分配。
Durable, persistent events and actions are persisted to disk, and will therefore be recovered if Business events or the underlying messaging provider restarts.
持续性、持久性事件和动作被持久化到磁盘，因此会在BusinessEvents或底层消息提供程序重启时得到恢复。
If you see disk contention when using sib persistent messaging and want to move the message store to a different, possibly faster disk location, follow the instructions here.
如果在使用SIB持久化消息传递时发现磁盘资源争用现象，并希望将消息存储库迁移到更快的远程磁盘驱动器，请遵循以下说明。
This means that you can have a persistent store behind the RMD, so the acknowledgement is only sent when the message has been written to disk.
在这个实现中，只有消息被持久化到磁盘后才会发出确认消息。
The initrd is also useful as a non-persistent root file system mounted in a RAM disk for embedded Linux systems.
initrd对于在嵌入式系统中加载到RAM磁盘里的非持久性根文件系统来说也非常有用。
The default disk mode is persistent.
默认的盘模式是persistent。
VMware has three different disk modes: persistent, doable and undoable.
VMware有三种不同的盘模式：persistent、doable和undoable。
AIX 5l Version 5.3 extends the JFS2 functionality by implementing disk usage quotas to control usage of persistent storage.
通过实现磁盘使用配额来控制永久存储的使用，AIX5lVersion 5.3扩展了JFS2的功能。
AIX 5l Version 5.3 extends the JFS2 functionality by implementing disk usage quotas to control usage of persistent storage.
通过实现磁盘使用配额来控制永久存储的使用，AIX5lVersion 5.3扩展了JFS2的功能。
应用推荐