Parallel processing RevoScaleR的RXEC不会进行并行处理

Parallel processing RevoScaleR的RXEC不会进行并行处理,parallel-processing,sql-server-2016,revoscaler,Parallel Processing,Sql Server 2016,Revoscaler,使用SQL Server 2016 R服务(在数据库中)测试RevoScaleR包带来的并行处理。下面是Microsoft提供的示例。然而,不像文档中所说的那样,我没有看到并行发生。有人知道为什么吗 SQL Server是在本地安装的,共有8个核心。在该示例上进行的唯一额外设置是: 为RXEC设置elemType='cores' 为RxInSqlServer设置consoleOutput=TRUE 我在T-SQL中的测试脚本是: EXEC sp\u execute\u external\u

使用SQL Server 2016 R服务(在数据库中)测试RevoScaleR包带来的并行处理。下面是Microsoft提供的示例。然而,不像文档中所说的那样,我没有看到并行发生。有人知道为什么吗

SQL Server是在本地安装的,共有8个核心。在该示例上进行的唯一额外设置是:

  • 为RXEC设置elemType='cores'

  • 为RxInSqlServer设置consoleOutput=TRUE

我在T-SQL中的测试脚本是:

EXEC sp\u execute\u external\u script@language=N'R',
@脚本=N'
#设置连接字符串

sqlConnString微软的文档似乎有误导性。将计算上下文更改为RxInSqlServer似乎不是并行的,而是使用RxLocalParallel

STDOUT message(s) from external script: 
======  WIN-6L7QANR32DF  ( process  1 ) has started run at  2019-08-29 11:37:10.60  ====== 
R Process ID = 7620 started at 2019-08-29 11:37:10.97 
R Process ID = 7620completed at 2019-08-29 11:37:11.03 
======  WIN-6L7QANR32DF  ( process  1 ) has completed run at  2019-08-29 11:37:11.08  ====== 
======  WIN-6L7QANR32DF  ( process  1 ) has started run at  2019-08-29 11:37:12.27  ====== 
R Process ID = 9072 started at 2019-08-29 11:37:12.80 
R Process ID = 9072completed at 2019-08-29 11:37:12.84 
======  WIN-6L7QANR32DF  ( process  1 ) has completed run at  2019-08-29 11:37:12.88  ====== 
======  WIN-6L7QANR32DF  ( process  1 ) has started run at  2019-08-29 11:37:14.29  ====== 
R Process ID = 8728 started at 2019-08-29 11:37:15.07 
R Process ID = 8728completed at 2019-08-29 11:37:15.10 
======  WIN-6L7QANR32DF  ( process  1 ) has completed run at  2019-08-29 11:37:15.15  ====== 
STDOUT message(s) from external script: 
======  WIN-6L7QANR32DF  ( process  1 ) has started run at  2019-08-29 11:37:16.31  ====== 
R Process ID = 8444 started at 2019-08-29 11:37:16.87 
R Process ID = 8444completed at 2019-08-29 11:37:16.91 
======  WIN-6L7QANR32DF  ( process  1 ) has completed run at  2019-08-29 11:37:16.97  ====== 
======  WIN-6L7QANR32DF  ( process  1 ) has started run at  2019-08-29 11:37:18.18  ====== 
R Process ID = 8244 started at 2019-08-29 11:37:18.72 
R Process ID = 8244completed at 2019-08-29 11:37:18.85 
======  WIN-6L7QANR32DF  ( process  1 ) has completed run at  2019-08-29 11:37:18.93  ====== 
======  WIN-6L7QANR32DF  ( process  1 ) has started run at  2019-08-29 11:37:20.00  ====== 
R Process ID = 2332 started at 2019-08-29 11:37:20.54 
R Process ID = 2332completed at 2019-08-29 11:37:20.59 
======  WIN-6L7QANR32DF  ( process  1 ) has completed run at  2019-08-29 11:37:20.63  ====== 
STDOUT message(s) from external script: 
======  WIN-6L7QANR32DF  ( process  1 ) has started run at  2019-08-29 11:37:21.62  ====== 
R Process ID = 336 started at 2019-08-29 11:37:22.24 
R Process ID = 336completed at 2019-08-29 11:37:22.27 
======  WIN-6L7QANR32DF  ( process  1 ) has completed run at  2019-08-29 11:37:22.32  ====== 
======  WIN-6L7QANR32DF  ( process  1 ) has started run at  2019-08-29 11:37:23.38  ====== 
R Process ID = 8280 started at 2019-08-29 11:37:23.88 
R Process ID = 8280completed at 2019-08-29 11:37:23.91 
======  WIN-6L7QANR32DF  ( process  1 ) has completed run at  2019-08-29 11:37:23.96  ======