Hi!

Thank you Janardhan, for organizing this. I think it's a great idea.

On 08.11.21 23:02, arnab phani wrote:
> Ideally, we should execute all/most of the tests with GPU enabled.
> However, given that GPU-specific code changes are limited, I agree that we
> can start slowly.
> 

Imho we should only run GPU tests where it makes sense. Many operations
are not even supported - so these can already be ruled out. And there
are also many operations where GPU operations don't give much benefit,
which in turn is a reason why not everything is supported on GPU.

So having a GPU runner that executes tests in the test.gpu namespace and
filling that with meaningful tests is a good first way to go imho.

Regards,
Mark

> Regards,
> Arnab..
> 
> On Mon, Nov 8, 2021 at 10:57 PM Baunsgaard, Sebastian
> <baunsga...@tugraz.at.invalid> wrote:
> 
>> Grat topic.
>>
>> It would be nice if we could use some small GPU cloud instances on demand
>> then maybe we can find some budget if it is not to large a cost.
>>
>> Best regards
>> Sebastian
>> ________________________________
>> From: Janardhan <janard...@apache.org>
>> Sent: Monday, November 8, 2021 7:30:00 PM
>> To: dev@systemds.apache.org
>> Subject: [DISCUSS][SYSTEMDS-3210] Self hosted runner for the GPU
>> integration test suite
>>
>> Hi all,
>>
>> TL;DR Integration test for GPU with self hosted runners
>>
>> Our integration tests span most of the system including basic checks for
>> docs.
>>
>> One component where we would be needing extensive testing would be GPU,
>> for this although GPU specific machines are not available on the GitHub
>> workflow
>> we with the help self hosted runners [1] could run the testing the
>> same way current testing is done.
>>
>> As a starting point, I have implemented this feature on my fork [2] as
>> an experimental feature. Planning to also be in touch with INFRA. I am
>> planning to run this action every saturday and PRs touching the gpu
>> component
>> as per the suggestion made by Mark (thank you!).
>>
>> Hoping that it helps keep confidence in that part of the code and also
>> remove the cognitive burden on the gpu devs. :)
>>
>> --
>> [1]
>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.github.com%2Fen%2Factions%2Fhosting-your-own-runners%2Fabout-self-hosted-runners&amp;data=04%7C01%7Cmdokter%40know-center.at%7Cde48b1b6aa364186d86d08d9a3038ae7%7C0d3c92e977ae4f49bd126ff29e8f1c37%7C0%7C0%7C637720057884574603%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=TGMIB2rVfFRivA%2BCROqqEXWhfubz4%2BHN9URrYaPuU9c%3D&amp;reserved=0
>> [2] 
>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fj143%2Fsystemds%2Fcommits%2Fmain-gpu&amp;data=04%7C01%7Cmdokter%40know-center.at%7Cde48b1b6aa364186d86d08d9a3038ae7%7C0d3c92e977ae4f49bd126ff29e8f1c37%7C0%7C0%7C637720057884574603%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=UaG4l22JDqSZ40n1leE5%2FSU08sX3Syca3%2FzbntDo7z4%3D&amp;reserved=0
>>
>> Thank you,
>> Janardhan
>>
> 

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to