Property reference

com.glide.concurrent_import_set_insert_mutex_spin_wait

The com.glide.concurrent_import_set_insert_mutex_spin_wait property defines the wait time in milliseconds for a mutex lock during concurrent import set operations. Admins should review this setting to optimize performance during data imports, especially when dealing with large datasets.

Default
1000
Type
integer
Application
Not stated

Key questions about this property

The answers below summarize the purpose, scope, default effect, and review scenarios for this property.

What does it do? This property sets the duration for which a mutex will wait if it acquires a lock during concurrent import processes, impacting import efficiency.
What area does it affect? Data import operations
What does the default mean? The default value is "1000", which sets the baseline numeric behavior for this property.
When should you review it? Review this property when configuring import settings or troubleshooting performance issues during data imports.

Property record

Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.

Property name com.glide.concurrent_import_set_insert_mutex_spin_wait
Type integer
Application Not stated
Default value 1000
Description Not stated

Sources

Official references and nearby text excerpts where this property appears.

Context preview Snippet 1
... a system property Concurrent import sets properties glide.scheduled_import.max.concurrent.import_sets Maximum number of import sets for one concurrent import. • Type: Integer • Default value: 10 • Location: Add a system property com.glide.concurrent_import_set_insert_mutex_spin_wait Wait time mutex spends if the lock is acquired (in milliseconds). • Type: Integer • Default value: 1000 • Location: Add a system property com.glide.concurrent_import_set_insert_mutex_expiration Mutex expiration time (in milliseconds). ...

More in com.glide

Other properties in the same namespace.

All 831 properties in com.glide →