27.12. Object Manager

27.12. Object Manager
Prev	Chapter 27. Understanding Configuration Values Related to the Core	Next

Configuration of the object manager:

busy_time_limit : float = 0.25 
debug_force_random_local_migration : boolean = false  
debug_force_swap_out_of_objects_with_scheduled_events : boolean = false  
debug_random_local_migration_probability : float = 0 
log_events : boolean = false 
log_process_migration_messages : boolean = false 
max_schedule_delay : float = 4

	Set `statistics.too_busy` to `true` if time difference between ticks at level zero is greater that this limit.
	Whether to enable random local migrations - object that must be delivered to destination object is passed to migration protocol layer even thought destination object is local. Note: Ignored if the Core is not compiled in debug mode.
	Whether to swap-out all objects which have scheduled one or more events for current tick. The objects are swapped-out before any event is processed in current tick.
	Specifies probability of local migration if debug_force_random_local_migration is true. Should be in 0.0 to 1.0 range, other values may cause random behavior.
	Log each delivered_to() and delivery_failed() events. Should be used only for debug purposes because it can really slow down entire system.
	Log each migration message that is beeing processed.
	Warn if global schedule has been blocked by a "busy" object for at least `max_schedule_delay` seconds.

Prev	Up	Next
27.11. Node Database	Home	27.13. Path Manager