Re: Environment markers for GPU/CUDA availibility
Nick Coghlan <[email protected]>
| Newsgroups | gmane.comp.python.distutils.devel |
|---|---|
| Message-ID | <CADiSq7cT9a8cJw1McnckNpmo7nnF6jZm4_HppQQwD1s_cnZ5Ng@mail.gmail.com> |
On Mon., 3 Sep. 2018, 5:48 am Ronald Oussoren, <[email protected]> wrote: > > What’s the problem with including GPU and non-GPU variants of code in a > binary wheel other than the size of the wheel? I tend to prefer binaries > that work “everywhere", even if that requires some more work in building > binaries (such as including multiple variants of extensions to have > optimised code for different CPU variants, such as SSE and non-SSE variants > in the past). > As far as I'm aware, binary artifact size *is* the problem. It's just that once you're automatically building and pushing an artifact (or an image containing that artifact) to thousands or tens of thousands of managed systems, the wasted bandwidth from pushing redundant implementations of the same functionality becomes more of a concern than the convenience of being able to use the same artifact across multiple platforms. Cheers, Nick. -- Distutils-SIG mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/mm3/archives/list/[email protected]/message/FXQCCADA5CCGR5O2E3F3A3M2AZXF2DWB/