Python和sendfile[通俗易懂]

Python和sendfile[通俗易懂]sendfile(2)isaUNIXsystemcallwhichprovidesa“zero-copy”wayofcopyingdatafromonefiledescriptor(afile)toanother(asocket).Becausethiscopyingisdoneentirelywithinthekernel,sen…

大家好,又见面了,我是你们的朋友全栈君。

sendfile(2) is a UNIX system call which provides a “zero-copy” way of copying data from one file descriptor (a file) to another (a socket). Because this copying is done entirely within the kernel, sendfile(2) is more efficient than the combination of “file.read()” and “socket.send()”, which requires transferring data to and from user space.  This copying of the data twice imposes some performance and resource penalties which sendfile(2) syscall avoids; it also results in a single system call (and thus only one context switch), rather than the series of read(2) / write(2) system calls (each system call requiring a context switch) used internally for the data copying. A more exhaustive explanation of how sendfile(2) works is available here,  but long story short is that sending a file with sendfile() is usually twice as fast than using plain socket.send(). Typical applications which can benefit from using sendfile() are FTP and HTTP servers.

sendfile(2)是UNIX系统调用,它提供“零复制”方式将数据从一个文件描述符(一个文件)复制到另一个文件描述符(一个套接字)。 由于此复制完全在内核中完成,因此sendfile(2)比“ file.read()”和“ socket.send()”的组合更有效,后者需要在用户空间之间来回传输数据。 两次复制数据会造成一些性能和资源损失,这是sendcall(2)syscall避免的。 它还导致单个系统调用(因此只有一个上下文切换),而不是内部用于数据复制的一系列read(2) / write(2)系统调用(每个系统调用都需要上下文切换)。 关于sendfile(2)的工作原理的更详尽的解释可以在这里找到 ,但是长话短说,使用sendfile()发送文件通常比使用普通socket.send() 快两倍 。 可以从使用sendfile()中受益的典型应用是FTP和HTTP服务器。

socket.sendfile() ( socket.sendfile())

I recently contributed a patch for Python’s socket module which adds a high-level socket.sendfile() method (see full discussion at issue 17552). socket.sendfile() will transmit a file until EOF is reached by attempting to use os.sendfile(), if available, else it falls back on using plain socket.send(). Internally, it takes care of handling socket timeouts and provides two optional parameters to move the file offset or to send only a limited amount of bytes. I came up with this idea because getting all of that right is a bit tricky, so a generic wrapper seemed to be convenient to have. socket.sendfile() will make its appearance in Python 3.5.

我最近为Python的套接字模块提供了一个补丁,该补丁添加了一个高级socket.sendfile()方法(请参阅问题17552的完整讨论)。 socket.sendfile()将一直传输文件,直到尝试通过使用os.sendfile()达到EOF 为止(如果可用),否则将使用普通的socket.send()退回。 在内部,它负责处理套接字超时,并提供两个可选参数来移动文件偏移或仅发送有限数量的字节。 我想出了这个主意,是因为要正确地使用所有这些技巧有些棘手,因此使用通用包装器似乎很方便。 socket.sendfile()将在Python 3.5中显示。

sendfile和Python ( sendfile and Python)

sendfile(2) made its first appearance into the Python stdlib kind of late: Python 3.3. It was contributed by Ross Lagerwall and me in issue 10882. Since the patch didn’t make it into python 2.X and I wanted to use sendfile() in pyftpdlib I later decided to release it as a stand alone module working with older (2.5+) Python versions (see pysendfile project). Starting with version 3.5, Python will hopefully start using sendfile() more extensively, in details:

sendfile(2)首次出现在Python stdlib中:Python 3.3。 它由Ross Lagerwall和我在发行10882中贡献 。 由于该修补程序并未进入python 2.X,并且我想在pyftpdlib中使用sendfile(),因此我后来决定将其作为独立模块发布,与较旧的(2.5+)Python版本一起使用(请参阅pysendfile项目)。 从3.5版开始,Python有望开始更广泛地使用sendfile(),详细信息:

TransmitFile. Now that socket.sendfile() is in place it seems natural to add support for it as well (see
TransmitFile 。 现在socket.sendfile()就位了,添加它的支持似乎也很自然(请参阅
issue 21721).
发行21721 )。

反向移植到Python 2.6和2.7 ( Backport to Python 2.6 and 2.7)

For those of you who are interested in using socket.sendfile() with older Python 2.6 and 2.7 versions here’s a backport. It requires pysendfile modules to be installed. Full code including tests is hosted here.

对于那些对将Socket.sendfile()与旧版2.6和2.7版本一起使用感兴趣的人,这里提供了一个backport。 它需要安装pysendfile模块。 完整的代码(包括测试)位于此处

#!/usr/bin/env python

"""
This is a backport of socket.sendfile() for Python 2.6 and 2.7.
socket.sendfile() will be included in Python 3.5:
http://bugs.python.org/issue17552
Usage:

>>> import socket
>>> file = open("somefile.bin", "rb")
>>> sock = socket.create_connection(("localhost", 8021))
>>> sendfile(sock, file)
42319283
>>>
"""

import errno
import io
import os
import select
import socket
try:
    memoryview  # py 2.7 only
except NameError:
    memoryview = lambda x: x

if os.name == 'posix':
    import sendfile as pysendfile  # requires "pip install pysendfile"
else:
    pysendfile = None


_RETRY = frozenset((errno.EAGAIN, errno.EALREADY, errno.EWOULDBLOCK,
                    errno.EINPROGRESS))


class _GiveupOnSendfile(Exception):
    pass


if pysendfile is not None:

    def _sendfile_use_sendfile(sock, file, offset=0, count=None):
        _check_sendfile_params(sock, file, offset, count)
        sockno = sock.fileno()
        try:
            fileno = file.fileno()
        except (AttributeError, io.UnsupportedOperation) as err:
            raise _GiveupOnSendfile(err)  # not a regular file
        try:
            fsize = os.fstat(fileno).st_size
        except OSError:
            raise _GiveupOnSendfile(err)  # not a regular file
        if not fsize:
            return 0  # empty file
        blocksize = fsize if not count else count

        timeout = sock.gettimeout()
        if timeout == 0:
            raise ValueError("non-blocking sockets are not supported")
        # poll/select have the advantage of not requiring any
        # extra file descriptor, contrarily to epoll/kqueue
        # (also, they require a single syscall).
        if hasattr(select, 'poll'):
            if timeout is not None:
                timeout *= 1000
            pollster = select.poll()
            pollster.register(sockno, select.POLLOUT)

            def wait_for_fd():
                if pollster.poll(timeout) == []:
                    raise socket._socket.timeout('timed out')
        else:
            # call select() once in order to solicit ValueError in
            # case we run out of fds
            try:
                select.select([], [sockno], [], 0)
            except ValueError:
                raise _GiveupOnSendfile(err)

            def wait_for_fd():
                fds = select.select([], [sockno], [], timeout)
                if fds == ([], [], []):
                    raise socket._socket.timeout('timed out')

        total_sent = 0
        # localize variable access to minimize overhead
        os_sendfile = pysendfile.sendfile
        try:
            while True:
                if timeout:
                    wait_for_fd()
                if count:
                    blocksize = count - total_sent
                    if blocksize <= 0:
                        break
                try:
                    sent = os_sendfile(sockno, fileno, offset, blocksize)
                except OSError as err:
                    if err.errno in _RETRY:
                        # Block until the socket is ready to send some
                        # data; avoids hogging CPU resources.
                        wait_for_fd()
                    else:
                        if total_sent == 0:
                            # We can get here for different reasons, the main
                            # one being 'file' is not a regular mmap(2)-like
                            # file, in which case we'll fall back on using
                            # plain send().
                            raise _GiveupOnSendfile(err)
                        raise err
                else:
                    if sent == 0:
                        break  # EOF
                    offset += sent
                    total_sent += sent
            return total_sent
        finally:
            if total_sent > 0 and hasattr(file, 'seek'):
                file.seek(offset)
else:
    def _sendfile_use_sendfile(sock, file, offset=0, count=None):
        raise _GiveupOnSendfile(
            "sendfile() not available on this platform")


def _sendfile_use_send(sock, file, offset=0, count=None):
    _check_sendfile_params(sock, file, offset, count)
    if sock.gettimeout() == 0:
        raise ValueError("non-blocking sockets are not supported")
    if offset:
        file.seek(offset)
    blocksize = min(count, 8192) if count else 8192
    total_sent = 0
    # localize variable access to minimize overhead
    file_read = file.read
    sock_send = sock.send
    try:
        while True:
            if count:
                blocksize = min(count - total_sent, blocksize)
                if blocksize <= 0:
                    break
            data = memoryview(file_read(blocksize))
            if not data:
                break  # EOF
            while True:
                try:
                    sent = sock_send(data)
                except OSError as err:
                    if err.errno in _RETRY:
                        continue
                    raise
                else:
                    total_sent += sent
                    if sent < len(data):
                        data = data[sent:]
                    else:
                        break
        return total_sent
    finally:
        if total_sent > 0 and hasattr(file, 'seek'):
            file.seek(offset + total_sent)


def _check_sendfile_params(sock, file, offset, count):
    if 'b' not in getattr(file, 'mode', 'b'):
        raise ValueError("file should be opened in binary mode")
    if not sock.type & socket.SOCK_STREAM:
        raise ValueError("only SOCK_STREAM type sockets are supported")
    if count is not None:
        if not isinstance(count, int):
            raise TypeError(
                "count must be a positive integer (got %s)" % repr(count))
        if count <= 0:
            raise ValueError(
                "count must be a positive integer (got %s)" % repr(count))


def sendfile(sock, file, offset=0, count=None):
    """sendfile(sock, file[, offset[, count]]) -> sent

    Send a *file* over a connected socket *sock* until EOF is
    reached by using high-performance sendfile(2) and return the
    total number of bytes which were sent.
    *file* must be a regular file object opened in binary mode.
    If sendfile() is not available (e.g. Windows) or file is
    not a regular file socket.send() will be used instead.
    *offset* tells from where to start reading the file.
    If specified, *count* is the total number of bytes to transmit
    as opposed to sending the file until EOF is reached.
    File position is updated on return or also in case of error in
    which case file.tell() can be used to figure out the number of
    bytes which were sent.
    The socket must be of SOCK_STREAM type.
    Non-blocking sockets are not supported.
    """
    try:
        return _sendfile_use_sendfile(sock, file, offset, count)
    except _GiveupOnSendfile:
        return _sendfile_use_send(sock, file, offset, count)


翻译自: https://www.pybloggers.com/2014/06/python-and-sendfile/

版权声明:本文内容由互联网用户自发贡献,该文观点仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请联系我们举报,一经查实,本站将立刻删除。

发布者:全栈程序员-站长,转载请注明出处:https://javaforall.net/135048.html原文链接:https://javaforall.net

(0)
全栈程序员-站长的头像全栈程序员-站长


相关推荐

  • docker(2)CentOS 7安装docker环境

    docker(2)CentOS 7安装docker环境前言前面一篇学了mac安装docker,这篇来学习在linux上安装docker环境准备Docker支持以下的CentOS版本,目前,CentOS仅发行版本中的内核支持Docker。Doc

    2022年8月6日
    6
  • Stopwatch类的使用

    Stopwatch类的使用Stopwatch类提供了一种方便的机制来测量运行时间。Stopwatch使用了操作系统和硬件提供的最高分辨率机制,通常少于1毫秒(相比之下DateTime.Now和Environment.TickCount的分辨率在15毫秒左右)。要使用Stopwatch,可以调用StartNew方法。这将会实例化一个Stopwatch对象并开始计时(此外,也可以先实例化,再手动调用Start方法)。Elap…

    2022年6月23日
    58
  • java中hashcode的用法_java底层原理面试题

    java中hashcode的用法_java底层原理面试题1.HashCode的特性(1)HashCode的存在主要是用于查找的快捷性,如Hashtable,HashMap等,HashCode经常用于确定对象的存储地址;(2)如果两个对象相同,equals方法一定返回true,并且这两个对象的HashCode一定相同;(3)两个对象的HashCode相同,并不一定表示两个对象就相同,即equals()不一定为true,只能说明这两…

    2025年10月8日
    2
  • java基础内容总结

    java基础内容总结

    2021年9月29日
    46
  • 使用secureCRT连接超时(最详细最有效的解决,就这一篇就够了)

    使用secureCRT连接超时(最详细最有效的解决,就这一篇就够了)从昨天下午到现在,可谓是一波三折,在网上查阅的文章不下100篇,结果很多都是没用的千篇一律,即使一些浏览器破千的文章,发现都是无头无尾,整个逻辑都很烂,最终通过一次次的失败到最后的成功使我不得不写篇指导,好让你们可以一次性解决问题,减少你们宝贵的时间,话不多话,现在开始吧!(开始之前,确保你们的Linux网络配置可以联网,输入pingwww.baidu.com),若不成功,则先去这里,把网络配…

    2022年5月13日
    61
  • Three.js呈现3D效果机房–初步方案[通俗易懂]

    Three.js呈现3D效果机房–初步方案[通俗易懂]3D机房系统是最近用户的需求,通过相关了解最后使用Three.js,也发现最近有东西可以写出来分享:webGL可以让我们在canvas上实现3D效果。而three.js是一款webGL框架,由于其易用性被广泛应用Three.js是通过对WebGL接口的封装与简化而形成的一个易用的图形库分步实现3D效果初始化3D模型参数开始搭建场景初始化渲染器初始化摄像机创建场景灯光布置创建网格线

    2022年5月29日
    48

发表回复

您的邮箱地址不会被公开。 必填项已用 * 标注

关注全栈程序员社区公众号