Parameter:
AdminPWakeupTimeShort description: Wait time after server start before the Administration Process (
adminp) becomes active for the first time – protects the freshly started server from load spikes.Profile
Parameter | AdminPWakeupTime |
Category | General |
Component | Server |
Available since | 10.0 |
Supported versions | 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1 |
GUI equivalent | Server document |
Possible values | Minutes as integer (default 2, typically 0–10) |
Description
After a server start many tasks are active simultaneously (Replicator, Indexer, Router, HTTP initialization, ...). To prevent the
AdminP task from generating additional load during this critical phase, it waits the number of minutes defined in AdminPWakeupTime after start before processing its queue (admin4.nsf) for the first time.The default value of
2 minutes is uncritical for typical servers. On heavily loaded hubs it can be increased to avoid contention with other start tasks; on test servers, where you want to see results quickly, it can be reduced to 0.Once set, it controls only the first run after start – the cyclic processing afterwards is governed by
AdminPInterval.Example configuration
AdminPWakeupTime=5
Notes & pitfalls
- Value in minutes.
- Affects only the first run after server start; afterwards
AdminPIntervalapplies.
- You can manually trigger processing at any time via
tell adminp process all.
- Takes effect after a server restart.
- Complementary to
AdminPInterval,AdminPModifyPersonDocumentsAt.