The Multi-Container Web server allows the division of a single web request into independent portions to be executed in parallel over different communication channels. To achieve this, the underlying communication infrastructure of traditional web environments is changed from the state-full TCP to the stateless UDP communication protocol. Such an architectural change provided an environment suitable for parallelization and distribution and enhanced some other already existing characteristics of the current web environments such as fault tolerance and web caching. In this paper, performance is further enhanced as part of the framework upon which web applications will run by introducing a number of changes. The configuration Manager (CM) is the subsystem that is responsible for reading configuration files provided by administrator. The CM is split into two parts, which are the Container CM and the HPA CM. After the CM reads the necessary configuration files and validates its content, it makes it easy for the administrators to be able to change environment setting such as container port ranges, types of nodes, services names, services location, number of instances each service should be loaded, and more. The CM also have the capability to reconstruct some types of configuration files from its data structure buffers, as such buffers may change through other subsystems and such changes may need to be permanent.