# No Op Engine ``` generic_message_store_engine=vmq_storage_engine_no_op ``` This implementation of message store does not persist messages to the disk. ## Tradeoffs When a node in a VerneMQ cluster restarts, it tries to load from the disk, all it's messages before it was shutdown. We have seen that this process is very CPU intensive and time-taking, and it may so happen that the node may not be able to join the cluster. This config allows the node to restart and join the cluster because it does not have to build it's messages from the disk. The drawback is that all the messages that were not synced with other nodes before the node got killed will be lost. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://courier-gojek.gitbook.io/vernemq/configuring-vernemq/noopengine.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.