从不同的goroutines制作昂贵的系统调用是否有意义?

时间:2017-03-18 10:19:46

标签: multithreading go system-calls goroutine

如果应用程序使用多个文件描述符(例如,打开 - 写入数据 - 同步 - 关闭)做了一些繁重的工作,那么Go运行时会发生什么?当昂贵的系统调用发生时(例如syscall.Fsync),它是否会阻止所有goroutine?或者只有调用goroutine被阻止而其他人仍在运行?

编写具有多个用户空间的多个工作程序的程序是否有意义 - 内核空间上下文切换?将多线程模式用于磁盘输入是否有意义?

package main

import (
    "log"
    "os"
    "sync"
)

var data = []byte("some big data")

func worker(filenamechan chan string, wg *sync.waitgroup) {
    defer wg.done()
    for {
        filename, ok := <-filenamechan
        if !ok {
            return
        }

        // open file is a quite expensive operation due to
        // the opening new descriptor
        f, err := os.openfile(filename, os.o_create|os.o_wronly, os.filemode(0644))
        if err != nil {
            log.fatal(err)
            continue
        }

        // write is a cheap operation,
        // because it just moves data from user space to the kernel space
        if _, err := f.write(data); err != nil {
            log.fatal(err)
            continue
        }

        // syscall.fsync is a disk-bound expensive operation
        if err := f.sync(); err != nil {
            log.fatal(err)
            continue
        }

        if err := f.close(); err != nil {
            log.fatal(err)
        }
    }
}

func main() {

    // launch workers
    filenamechan := make(chan string)
    wg := &sync.waitgroup{}
    for i := 0; i < 2; i++ {
        wg.add(1)
        go worker(filenamechan, wg)
    }

    // send tasks to workers
    filenames := []string{
        "1.txt",
        "2.txt",
        "3.txt",
        "4.txt",
        "5.txt",
    }
    for i := range filenames {
        filenamechan <- filenames[i]
    }
    close(filenamechan)

    wg.wait()
}

https://play.golang.org/p/O0omcPBMAJ

1 个答案:

答案 0 :(得分:4)

如果系统调用阻塞,Go运行时将启动一个新线程,以便运行goroutine的线程数保持不变。

可在此处找到更全面的解释:https://morsmachine.dk/go-scheduler