Apex.ai, Inc.

Misha Shalem

Michael Pöhnl

Alban Tamisier

In current frameworks, replays of events (e.g., data communications) between software entities are non-deterministic and unreproducible. In an embodiment, as events are replayed, software entities, stimulated by those events, are queued according to a queuing strategy and executed from the queue. In an alternative embodiment, as software entities are executed, the events, output by those software entities, are queued according to a queuing strategy and played from the queue.

Deterministic replay of events between software entities

Deterministic memory allocation for real-time applications. In an embodiment, bitcode is scanned to detect calls by a memory allocation function to a dummy function. Each call uses parameters comprising an identifier of a memory pool and a size of a data type to be stored in the memory pool. For each detected call, an allocation record, comprising the parameters, is generated. Then, a header file is generated based on the allocation records. The header file may comprise a definition of bucket(s) and a definition of memory pools. Each definition of a memory pool may identify at least one bucket.

Deterministic memory allocation for real-time applications

The replay of events (e.g., data communications) between software entities should be deterministic and reproducible. In the disclosed framework, as events are replayed, software entities, stimulated by those events, are enqueued according to a queuing strategy and executed from the queue. Alternatively, as software entities are executed, the events, output by those software entities, are queued according to a queuing strategy and played from the queue.

Growing community of inventors

Zichron Yaakov, Israel

Misha Shalem