# Bundle Pool Management

Eclipse's provisioning technology, p2, manages each Eclipse installation using a so-called agent. The agent maintains and manages one or more bundle pools, which contains the artifacts (plug-ins and features) used by the installation, as well as one or more profiles, which specify precisely which artifacts are currently in use by that installation. Creating an initial installation, installing new software into the installation, or updating the installation with the latest software work via the agent. An agent can be co-located with a single installation or an agent can be a shared agent that manages multiple installations. By default, Oomph will use a shared agent which has the advantage that multiple installations share artifacts, dramatically reducing disk space.

In this dialog you can manage the disk locations of your shared agents as well as the disk locations of each of the agent's bundle pools. The pools can get large over time and can accumulate so called garbage, e.g., if you delete an installation, its profile will become unused, or if you update an installation, some of the older artifacts may become unused. This dialog allows you to perform garbage collection, i.e., allows you to cleanup the shared agent. You can also do a more detailed analysis of the agent to detect damaged artifacts and to repair them. In addition, p2 caches repository metadata to speed up peformance; this dialog allows the agent's repository metadata cache to be cleared.

This dialog can even be used to show all the profiles of the installations managed by each agent and can be used to inspect the details of each profile.