Why does UndoDB create lots of strange processes?

UndoDB creates many extra processes, often up to thirty in normal operation.

As an example, when I run the cache_x64 demo application in UndoDB, I see the following process listing:

12760 pts/8 t 0:00 /home/tperry/Downloads/undodb-4.3.3521/examples/cache_x64
12764 pts/8 S 0:00 [undodb-cl-12760]
12766 pts/8 t 0:00 /home/tperry/Downloads/undodb-4.3.3521/examples/cache_x64
12768 pts/8 t 0:00 undodb-ss-12760 12770 pts/8 t 0:00 undodb-ss-12760
12772 pts/8 t 0:00 undodb-ss-12760 12774 pts/8 t 0:00 undodb-ss-12760
12776 pts/8 t 0:00 undodb-ss-12760 12778 pts/8 t 0:00 undodb-ss-12760
12780 pts/8 t 0:00 undodb-ss-12760 12782 pts/8 t 0:00 undodb-ss-12760

The undodb-ss processes are copy-on-write process snapshots, which are crucial to the UndoDB recording technology.  The undodb-cl process is an internal UndoDB process which manages the snapshots.

For more information, see the documentation for the --undodb-snapshots command-line option.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk