Property reference

com.glide.concurrent_import_set_mutex_fast_lock

The com.glide.concurrent_import_set_mutex_fast_lock property determines whether to use a fast lock mechanism or a slower SQL-based lock for concurrent import sets. Admins should consider enabling this property to improve performance during high-volume data imports.

Default
false
Type
boolean
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 toggles between fast locking and SQL-based locking for concurrent import sets, affecting how data is processed during imports.
What area does it affect? Concurrent import sets
What does the default mean? The default value is "false", which means this behavior is disabled by default.
When should you review it? Review this property when optimizing import performance or troubleshooting import set issues.

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_mutex_fast_lock
Type boolean
Application Not stated
Default value false
Description Not stated

Sources

Official references and nearby text excerpts where this property appears.

Context preview Snippet 1
... Integer • Default value: 1000 • Location: Add a system property com.glide.concurrent_import_set_insert_mutex_expiration Mutex expiration time (in milliseconds). • Type: Integer • Default value: 300000 • Location: Add a system property com.glide.concurrent_import_set_mutex_fast_lock Specifies whether to use fast lock (true) or SQL-based slow lock (false). • Type: true | false • Default value: false • Location: Add a system property Web service import ...

More in com.glide

Other properties in the same namespace.

All 831 properties in com.glide →