Making Rust respect worker count in config

Martin von Zweigbergk martinvonz at google.com
Thu Nov 7 11:08:32 EST 2019


Seems fine to do that every time we read configs in Python. It won't always
be correct if there are multiple values for it in different config files
(e.g. repo-specific vs user's config). Probably good enough.

On Thu, Nov 7, 2019, 07:54 Raphaël Gomès <raphael.gomes at octobus.net> wrote:

> I'd like to make Rust respect to max worker count in config, since it
> now runs parallel code. Right now, it uses every CPU available, be it
> logical or physical.
>
> I think the simplest way to do so, since Rust does not yet know how to
> read the config file, is to set the RAYON_NUM_THREADS environment
> variable in the Python layer as soon as possible.
>
> I'm unsure where to do it though and what the implications are
> cross-platform. Maybe as soon as the config is loaded?
>
> Thanks,
>
> Raphaël
>
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20191107/788d1ce9/attachment.html>


More information about the Mercurial-devel mailing list