Portal Manager and Infopark Search Cartridge

A large number of personalization requests to a portal can cause high load which leads to performance collapses. If the Portal Manager is running on the same system as the webserver, non-personalized documents will be delivered late as well. If, however, the Portal Manager is operated on a separate machine, non-personalized documents are still available, even if the Portal Manager’s reaction is delayed because the hardware is working at full capacity.

This is also true for the Search Server which is part of the Infopark Search Cartridge. If the Server is run on a separate computer, a large number of simultaneous search requests will not automatically cause dynamic documents to be delivered with a delay as well.