don't be confused about internal process time and external wall clock time here.
On Sun, Sep 16, 2018 at 11:27 AM Thomas Solignac <soligna...@gmail.com> wrote: > I think the concurrent read overhead compensates the process > parallelization ! > > Both files are in attachment. > > Thank you for helping :-) > > > > Le dimanche 16 septembre 2018 20:02:33 UTC+2, Marc Zahn a écrit : >> >> You mean, loading the files in parallel take the ~same time as loading >> them sequentially? It seems that there is somewhere else a bottleneck... >> >> Am Sonntag, 16. September 2018 14:08:50 UTC+2 schrieb Thomas Solignac: >>> >>> Hello, >>> >>> I have a loading step, where I have something like 60 files to read and >>> process, as fast as possible. >>> I tried loading with goroutines and without, and I get substantially the >>> same process time (38s). >>> >>> *What is the more idiomatic ? Is Golang designed for concurrent files >>> I/O ?* >>> >>> Note : One file per goroutine (not multiple concurents I/O on the same >>> file) >>> >>> Thanks for reading :-) >>> >> -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- *Michael T. jonesmichael.jo...@gmail.com <michael.jo...@gmail.com>* -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
