runAsync doesn't work the same as ACF2018

Description

From samples from the adobe site, it appears that sleep() is non-blocking in ACF2018. That makes testing runAsync() easier since the times are additive if the gets are not running simultaneously and non-additive if not. This is shown by the examples in the reference above. For example, having four gets results in execution time of 4.002 seconds. (same as slowest process) Having one "get" results in execution time of 10.002 seconds. (same as adding all process times together)

Environment

Windows 10 - Lucee release 5.3.1.102

relates to

Activity

Show:

Details

Assignee

Reporter

Priority

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Affects versions

Created 16 April 2019 at 22:32
Updated 17 February 2023 at 03:02

Flag notifications