如何使用多处理来解决令人尴尬的并行问题?
令人尴尬的并行问题通常由三个基本部分组成:
- 读取输入数据(从文件、数据库、tcp 连接等)。
- 对输入数据运行计算,其中每个计算独立于任何其他计算。
- 写入计算结果(写入文件、数据库、tcp 连接等)。
我们可以在两个维度上并行化程序:
- 第 2 部分可以在多个内核上运行,因为每个计算都是独立的;处理顺序并不重要。
- 每个部分都可以独立运行。第 1 部分可以将数据放入输入队列,第 2 部分可以从输入队列中取出数据并将结果放入输出队列,第 3 部分可以从输出队列中取出结果并将其写出。
这似乎是并发编程中最基本的模式,但我仍然迷失在尝试解决它的过程中,所以让我们编写一个规范的示例来说明如何使用多处理来完成此操作。
以下是示例问题:给定一个以整数行作为输入的 CSV 文件,计算它们的值总和。将问题分为三个部分,它们都可以并行运行:
- 将输入文件处理为原始数据(整数的列表/迭代)
- 并行计算数据的总和
- 输出总和
下面是传统的单进程绑定 Python 程序它解决了这三个任务:
#!/usr/bin/env python
# -*- coding: UTF-8 -*-
# basicsums.py
"""A program that reads integer values from a CSV file and writes out their
sums to another CSV file.
"""
import csv
import optparse
import sys
def make_cli_parser():
"""Make the command line interface parser."""
usage = "\n\n".join(["python %prog INPUT_CSV OUTPUT_CSV",
__doc__,
"""
ARGUMENTS:
INPUT_CSV: an input CSV file with rows of numbers
OUTPUT_CSV: an output file that will contain the sums\
"""])
cli_parser = optparse.OptionParser(usage)
return cli_parser
def parse_input_csv(csvfile):
"""Parses the input CSV and yields tuples with the index of the row
as the first element, and the integers of the row as the second
element.
The index is zero-index based.
:Parameters:
- `csvfile`: a `csv.reader` instance
"""
for i, row in enumerate(csvfile):
row = [int(entry) for entry in row]
yield i, row
def sum_rows(rows):
"""Yields a tuple with the index of each input list of integers
as the first element, and the sum of the list of integers as the
second element.
The index is zero-index based.
:Parameters:
- `rows`: an iterable of tuples, with the index of the original row
as the first element, and a list of integers as the second element
"""
for i, row in rows:
yield i, sum(row)
def write_results(csvfile, results):
"""Writes a series of results to an outfile, where the first column
is the index of the original row of data, and the second column is
the result of the calculation.
The index is zero-index based.
:Parameters:
- `csvfile`: a `csv.writer` instance to which to write results
- `results`: an iterable of tuples, with the index (zero-based) of
the original row as the first element, and the calculated result
from that row as the second element
"""
for result_row in results:
csvfile.writerow(result_row)
def main(argv):
cli_parser = make_cli_parser()
opts, args = cli_parser.parse_args(argv)
if len(args) != 2:
cli_parser.error("Please provide an input file and output file.")
infile = open(args[0])
in_csvfile = csv.reader(infile)
outfile = open(args[1], 'w')
out_csvfile = csv.writer(outfile)
# gets an iterable of rows that's not yet evaluated
input_rows = parse_input_csv(in_csvfile)
# sends the rows iterable to sum_rows() for results iterable, but
# still not evaluated
result_rows = sum_rows(input_rows)
# finally evaluation takes place as a chain in write_results()
write_results(out_csvfile, result_rows)
infile.close()
outfile.close()
if __name__ == '__main__':
main(sys.argv[1:])
让我们使用这个程序并重写它以使用多处理来并行化上面概述的三个部分。下面是这个新的并行程序的框架,需要充实它以解决注释中的部分:
#!/usr/bin/env python
# -*- coding: UTF-8 -*-
# multiproc_sums.py
"""A program that reads integer values from a CSV file and writes out their
sums to another CSV file, using multiple processes if desired.
"""
import csv
import multiprocessing
import optparse
import sys
NUM_PROCS = multiprocessing.cpu_count()
def make_cli_parser():
"""Make the command line interface parser."""
usage = "\n\n".join(["python %prog INPUT_CSV OUTPUT_CSV",
__doc__,
"""
ARGUMENTS:
INPUT_CSV: an input CSV file with rows of numbers
OUTPUT_CSV: an output file that will contain the sums\
"""])
cli_parser = optparse.OptionParser(usage)
cli_parser.add_option('-n', '--numprocs', type='int',
default=NUM_PROCS,
help="Number of processes to launch [DEFAULT: %default]")
return cli_parser
def main(argv):
cli_parser = make_cli_parser()
opts, args = cli_parser.parse_args(argv)
if len(args) != 2:
cli_parser.error("Please provide an input file and output file.")
infile = open(args[0])
in_csvfile = csv.reader(infile)
outfile = open(args[1], 'w')
out_csvfile = csv.writer(outfile)
# Parse the input file and add the parsed data to a queue for
# processing, possibly chunking to decrease communication between
# processes.
# Process the parsed data as soon as any (chunks) appear on the
# queue, using as many processes as allotted by the user
# (opts.numprocs); place results on a queue for output.
#
# Terminate processes when the parser stops putting data in the
# input queue.
# Write the results to disk as soon as they appear on the output
# queue.
# Ensure all child processes have terminated.
# Clean up files.
infile.close()
outfile.close()
if __name__ == '__main__':
main(sys.argv[1:])
这些代码片段,以及 另一段可以生成示例 CSV 文件的代码用于测试目的,可以是 在 github 上找到。
对于并发专家如何解决这个问题的任何见解,我将不胜感激。
这是我在考虑这个问题时遇到的一些问题。解决任何/所有问题的加分点:
- 我是否应该有子进程来读取数据并将其放入队列,或者主进程可以这样做在读取所有输入之前不会阻塞?
- 同样,我应该有一个子进程来从已处理的队列中写出结果,还是主进程可以执行此操作而不必等待所有结果?
- 我应该使用 进程池 进行求和操作吗?
- 假设我们不需要在数据输入时抽取输入和输出队列,而是可以等到所有输入都被解析并计算出所有结果(例如,因为我们知道所有输入和输出都适合系统内存)。我们是否应该以任何方式改变算法(例如,不与 I/O 同时运行任何进程)?
How does one use multiprocessing to tackle embarrassingly parallel problems?
Embarassingly parallel problems typically consist of three basic parts:
- Read input data (from a file, database, tcp connection, etc.).
- Run calculations on the input data, where each calculation is independent of any other calculation.
- Write results of calculations (to a file, database, tcp connection, etc.).
We can parallelize the program in two dimensions:
- Part 2 can run on multiple cores, since each calculation is independent; order of processing doesn't matter.
- Each part can run independently. Part 1 can place data on an input queue, part 2 can pull data off the input queue and put results onto an output queue, and part 3 can pull results off the output queue and write them out.
This seems a most basic pattern in concurrent programming, but I am still lost in trying to solve it, so let's write a canonical example to illustrate how this is done using multiprocessing.
Here is the example problem: Given a CSV file with rows of integers as input, compute their sums. Separate the problem into three parts, which can all run in parallel:
- Process the input file into raw data (lists/iterables of integers)
- Calculate the sums of the data, in parallel
- Output the sums
Below is traditional, single-process bound Python program which solves these three tasks:
#!/usr/bin/env python
# -*- coding: UTF-8 -*-
# basicsums.py
"""A program that reads integer values from a CSV file and writes out their
sums to another CSV file.
"""
import csv
import optparse
import sys
def make_cli_parser():
"""Make the command line interface parser."""
usage = "\n\n".join(["python %prog INPUT_CSV OUTPUT_CSV",
__doc__,
"""
ARGUMENTS:
INPUT_CSV: an input CSV file with rows of numbers
OUTPUT_CSV: an output file that will contain the sums\
"""])
cli_parser = optparse.OptionParser(usage)
return cli_parser
def parse_input_csv(csvfile):
"""Parses the input CSV and yields tuples with the index of the row
as the first element, and the integers of the row as the second
element.
The index is zero-index based.
:Parameters:
- `csvfile`: a `csv.reader` instance
"""
for i, row in enumerate(csvfile):
row = [int(entry) for entry in row]
yield i, row
def sum_rows(rows):
"""Yields a tuple with the index of each input list of integers
as the first element, and the sum of the list of integers as the
second element.
The index is zero-index based.
:Parameters:
- `rows`: an iterable of tuples, with the index of the original row
as the first element, and a list of integers as the second element
"""
for i, row in rows:
yield i, sum(row)
def write_results(csvfile, results):
"""Writes a series of results to an outfile, where the first column
is the index of the original row of data, and the second column is
the result of the calculation.
The index is zero-index based.
:Parameters:
- `csvfile`: a `csv.writer` instance to which to write results
- `results`: an iterable of tuples, with the index (zero-based) of
the original row as the first element, and the calculated result
from that row as the second element
"""
for result_row in results:
csvfile.writerow(result_row)
def main(argv):
cli_parser = make_cli_parser()
opts, args = cli_parser.parse_args(argv)
if len(args) != 2:
cli_parser.error("Please provide an input file and output file.")
infile = open(args[0])
in_csvfile = csv.reader(infile)
outfile = open(args[1], 'w')
out_csvfile = csv.writer(outfile)
# gets an iterable of rows that's not yet evaluated
input_rows = parse_input_csv(in_csvfile)
# sends the rows iterable to sum_rows() for results iterable, but
# still not evaluated
result_rows = sum_rows(input_rows)
# finally evaluation takes place as a chain in write_results()
write_results(out_csvfile, result_rows)
infile.close()
outfile.close()
if __name__ == '__main__':
main(sys.argv[1:])
Let's take this program and rewrite it to use multiprocessing to parallelize the three parts outlined above. Below is a skeleton of this new, parallelized program, that needs to be fleshed out to address the parts in the comments:
#!/usr/bin/env python
# -*- coding: UTF-8 -*-
# multiproc_sums.py
"""A program that reads integer values from a CSV file and writes out their
sums to another CSV file, using multiple processes if desired.
"""
import csv
import multiprocessing
import optparse
import sys
NUM_PROCS = multiprocessing.cpu_count()
def make_cli_parser():
"""Make the command line interface parser."""
usage = "\n\n".join(["python %prog INPUT_CSV OUTPUT_CSV",
__doc__,
"""
ARGUMENTS:
INPUT_CSV: an input CSV file with rows of numbers
OUTPUT_CSV: an output file that will contain the sums\
"""])
cli_parser = optparse.OptionParser(usage)
cli_parser.add_option('-n', '--numprocs', type='int',
default=NUM_PROCS,
help="Number of processes to launch [DEFAULT: %default]")
return cli_parser
def main(argv):
cli_parser = make_cli_parser()
opts, args = cli_parser.parse_args(argv)
if len(args) != 2:
cli_parser.error("Please provide an input file and output file.")
infile = open(args[0])
in_csvfile = csv.reader(infile)
outfile = open(args[1], 'w')
out_csvfile = csv.writer(outfile)
# Parse the input file and add the parsed data to a queue for
# processing, possibly chunking to decrease communication between
# processes.
# Process the parsed data as soon as any (chunks) appear on the
# queue, using as many processes as allotted by the user
# (opts.numprocs); place results on a queue for output.
#
# Terminate processes when the parser stops putting data in the
# input queue.
# Write the results to disk as soon as they appear on the output
# queue.
# Ensure all child processes have terminated.
# Clean up files.
infile.close()
outfile.close()
if __name__ == '__main__':
main(sys.argv[1:])
These pieces of code, as well as another piece of code that can generate example CSV files for testing purposes, can be found on github.
I would appreciate any insight here as to how you concurrency gurus would approach this problem.
Here are some questions I had when thinking about this problem. Bonus points for addressing any/all:
- Should I have child processes for reading in the data and placing it into the queue, or can the main process do this without blocking until all input is read?
- Likewise, should I have a child process for writing the results out from the processed queue, or can the main process do this without having to wait for all the results?
- Should I use a processes pool for the sum operations?
- Suppose we didn't need to siphon off the input and output queues as data entered them, but could wait until all input was parsed and all results were calculated (e.g., because we know all the input and output will fit in system memory). Should we change the algorithm in any way (e.g., not run any processes concurrently with I/O)?
发布评论
评论(5)
我的解决方案有一个额外的功能,以确保输出的顺序与输入的顺序相同。我使用 multiprocessing.queue 在进程之间发送数据,发送停止消息,以便每个进程都知道停止检查队列。我认为来源中的评论应该清楚地说明发生了什么,但如果没有让我知道。
My solution has an extra bell and whistle to make sure that the order of the output has the same as the order of the input. I use multiprocessing.queue's to send data between processes, sending stop messages so each process knows to quit checking the queues. I think the comments in the source should make it clear what's going on but if not let me know.
来晚了......
joblib 在多处理之上有一个层来帮助并行处理循环。除了非常简单的语法之外,它还为您提供了延迟调度作业和更好的错误报告等功能。
作为免责声明,我是 joblib 的原作者。
Coming late to the party...
joblib has a layer on top of multiprocessing to help making parallel for loops. It gives you facilities like a lazy dispatching of jobs, and better error reporting in addition to its very simple syntax.
As a disclaimer, I am the original author of joblib.
我意识到我参加聚会有点晚了,但我最近发现了 GNU 并行,并想展示用它完成这个典型任务是多么容易。
sum.py
会执行类似的操作:并行将为
input.csv
中的每一行运行sum.py
(当然,并行运行) ),然后将结果输出到sums
。明显比多处理
麻烦更好I realize that I'm a bit late for the party, but I've recently discovered GNU parallel, and want to show how easy it is to accomplish this typical task with it.
Something like this will do for
sum.py
:Parallel will run
sum.py
for every line ininput.csv
(in parallel, of course), then output the results tosums
. Clearly better thanmultiprocessing
hassle老派。
p1.py
p2.py
p3.py
这是多处理的最终结构。
是的,shell 在操作系统级别将它们编织在一起。对我来说这似乎更简单而且效果很好。
是的,使用 pickle(或 cPickle)的开销稍微多一些。然而,这种简化似乎值得付出努力。
如果您希望文件名成为
p1.py
的参数,这是一个简单的更改。更重要的是,像下面这样的函数非常方便。
这允许您执行此操作:
这非常简单,但它并不容易让您运行 P2.py 的多个副本。
您有两个问题:扇出和扇入。 P1.py 必须以某种方式扇出到多个 P2.py。 P2.py 必须以某种方式将其结果合并到单个 P3.py 中。
老式的扇出方法是“推”架构,这是非常有效的。
理论上,多个P2.py从一个公共队列中拉取是资源的最优分配。这通常是理想的,但它也是相当大量的编程。编程真的有必要吗?或者循环处理就足够了吗?
实际上,您会发现让 P1.py 在多个 P2.py 之间进行简单的“循环”处理可能非常好。您将 P1.py 配置为通过命名管道处理 P2.py 的 n 个副本。 P2.py 将从各自适当的管道中读取数据。
如果一个 P2.py 获取了所有“最坏情况”数据并且运行远远落后怎么办?是的,循环赛并不完美。但它比只有一个 P2.py 更好,您可以通过简单的随机化来解决这种偏差。
从多个 P2.py 扇入到一个 P3.py 还是有点复杂。此时,老式方法不再具有优势。 P3.py 需要使用
select
库从多个命名管道中读取数据以交错读取。Old School.
p1.py
p2.py
p3.py
Here's the multi-processing final structure.
Yes, the shell has knit these together at the OS level. It seems simpler to me and it works very nicely.
Yes, there's slightly more overhead in using pickle (or cPickle). The simplification, however, seems worth the effort.
If you want the filename to be an argument to
p1.py
, that's an easy change.More importantly, a function like the following is very handy.
That allows you to do this:
This is very simple, but it does not easily allow you to have multiple copies of P2.py running.
You have two problems: fan-out and fan-in. The P1.py must somehow fan out to multiple P2.py's. And the P2.py's must somehow merge their results into a single P3.py.
The old-school approach to fan-out is a "Push" architecture, which is very effective.
Theoretically, multiple P2.py's pulling from a common queue is the optimal allocation of resources. This is often ideal, but it's also a fair amount of programming. Is the programming really necessary? Or will round-robin processing be good enough?
Practically, you'll find that making P1.py do a simple "round robin" dealing among multiple P2.py's may be quite good. You'd have P1.py configured to deal to n copies of P2.py via named pipes. The P2.py's would each read from their appropriate pipe.
What if one P2.py gets all the "worst case" data and runs way behind? Yes, round-robin isn't perfect. But it's better than only one P2.py and you can address this bias with simple randomization.
Fan-in from multiple P2.py's to one P3.py is a bit more complex, still. At this point, the old-school approach stops being advantageous. P3.py needs to read from multiple named pipes using the
select
library to interleave the reads.在第 1 部分中也可能引入一些并行性。对于像 CSV 这样简单的格式来说可能不是问题,但如果输入数据的处理明显慢于数据的读取,您可以读取更大的块,然后继续读取,直到找到“行分隔符”( CSV 情况下的换行符,但这又取决于读取的格式;如果格式足够复杂,则不起作用)。
这些块(每个块可能包含多个条目)然后可以被分配给一群并行进程,从队列中读取作业,在其中对它们进行解析和拆分,然后将其放入第 2 阶段的队列中。
It's probably possible to introduce a bit of parallelism into part 1 as well. Probably not an issue with a format that's as simple as CSV, but if the processing of the input data is noticeably slower than the reading of the data, you could read larger chunks, then continue to read until you find a "row separator" (newline in the CSV case, but again that depends on the format read; doesn't work if the format is sufficiently complex).
These chunks, each probably containing multiple entries, can then be farmed off to a crowd of parallel processes reading jobs off a queue, where they're parsed and split, then placed on the in-queue for stage 2.