On Wed, Jun 29, 2016 at 10:01 PM, Eric Wong <e@xxxxxxxxx> wrote: > Christian Couder <christian.couder@xxxxxxxxx> wrote: >> Design discussion about performance >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> >> Yeah, it is not efficient to fork/exec a command to just read or write >> one object to or from the external ODB. Batch calls and/or using a >> daemon and/or RPC should be used instead to be able to store regular >> objects in an external ODB. But for now the external ODB would be all >> about really big files, where the cost of a fork+exec should not >> matter much. If we later want to extend usage of external ODBs, yeah >> we will probably need to design other mechanisms. > > I would also investigate switching run_command to use vfork+exec > or posix_spawn for performance (keeping in mind vfork > caveats documented at https://ewontfix.com/7/ ) Thanks Eric for this idea and the test! -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html