Quantopian's community platform is shutting down. Please read this post for more information and download your code.
Back to Community
Why the same algo in quantopian and local zipline has a big gap in the consuming time of backtest?

The backtest of algo in quantopian cost about few seconds, but the same algo with zipline in my local machine (docker, ) used 100% one of 5 cores and 649 M of 13.7 G Mem. The total time consumed is "CPU times: user 11min 20s, sys: 16.2 s, total: 11min 36s Wall time: 11min 35s". Is there something I misused this lib? Thanks!