You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@madlib.apache.org by "Ekta Khanna (JIRA)" <ji...@apache.org> on 2019/05/10 17:18:00 UTC
[jira] [Commented] (MADLIB-1308) Change GPU related hardcoded
things in madlib_keras.py_in
[ https://issues.apache.org/jira/browse/MADLIB-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837453#comment-16837453 ]
Ekta Khanna commented on MADLIB-1308:
-------------------------------------
https://github.com/apache/madlib/pull/383
> Change GPU related hardcoded things in madlib_keras.py_in
> ---------------------------------------------------------
>
> Key: MADLIB-1308
> URL: https://issues.apache.org/jira/browse/MADLIB-1308
> Project: Apache MADlib
> Issue Type: Improvement
> Components: Deep Learning
> Reporter: Nandish Jayaram
> Priority: Major
> Fix For: v1.16
>
>
> Based on the code in PR [https://github.com/apache/madlib/pull/355:]
> # Currently in madlib_keras.py_in , we hardcod the following things
> ## gpus_per_host = 4
> ## device_name = '/cpu:0' or '/gpu:0' ( can the device ever be not named gpu0 or cpu0 ? )
> # Look into and document the usage of {{CUDA_VISIBLE_DEVICES}} when gpu_only is set to TRUE. Currently we set it to str(current_seg_id % gpus_per_host). How does this logic work and will it always work? How would this logic change for Postgres, since it has no segment_id.
> # What happens if
> no of gpus < no of segments
> no of gpus > no of segments
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)