Threshold-Based Barrier Synchronization for Compute Processes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current synchronization mechanisms in computing systems are inefficient in expressing algorithmic-level semantics, particularly when a subset of processes need to interlock based on specific thresholds, leading to unnecessary synchronizations and impractical implementations.

Innovation Solution

Implementing a barrier-like synchronization mechanism with a release condition based on reaching a threshold of defined measures, such as the number of processes or data updated in a memory region, allowing for efficient partial synchronization in distributed or parallel computing environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional barrier synchronization is used to ensure all processes interlock, then reliability is improved, but productivity deteriorates due to unnecessary waiting and overhead

Engineering Contradiction:
Improvesynchronization correctnessVSAvoidcompute efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies partial synchronization by allowing a subset of processes to proceed when a threshold is reached, rather than requiring all processes to synchronize. This enables productive work to continue in parallel while maintaining correctness for the synchronized subset, resolving the contradiction between reliability and productivity.

Inventive Principle:
Principle #16Partial or excessive action

2Productivity

If threshold-based partial synchronization is implemented, then productivity is improved by reducing unnecessary waits, but device complexity increases due to threshold management overhead

Engineering Contradiction:
Improvecompute efficiencyVSAvoidsynchronization mechanism complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The synchronization mechanism automatically monitors process completion and threshold conditions, releasing processes self-managed when conditions are met. This automation reduces the perceived complexity for users while maintaining high productivity through intelligent threshold-based control.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If traditional barrier synchronization is used, then ease of operation is maintained with simple barrier interfaces, but loss of time increases due to forced waiting

Engineering Contradiction:
Improvesynchronization simplicityVSAvoidsynchronization waiting time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system performs partial synchronization only when thresholds are met, avoiding forced waiting for all processes. This maintains operational simplicity while dramatically reducing time loss by allowing productive processes to continue without unnecessary delays.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10824481B2Partial synchronization between compute tasks based on threshold specification in a computing system
Publication Date: 2020.11.03 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10824481B2 patent drawing
  • US10824481B2 patent drawing
  • US10824481B2 patent drawing

AI summary

Embodiments for implementing partial synchronization between compute processes based on threshold specification in a computing environment. One or more compute processes may be synchronized in one of a plurality of types of computing platforms using a barrier having a barrier release condition based on a threshold of one or more measures. The barrier is defined according to one or more parameters. The one or more compute processes may be released via the barrier upon exceeding the threshold of the one or more measures.