[ 
https://issues.apache.org/jira/browse/MXNET-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Olivier updated MXNET-25:
-------------------------------
    Component/s: MXNet Engine

> Convert created profiling objects to use ObjectPool
> ---------------------------------------------------
>
>                 Key: MXNET-25
>                 URL: https://issues.apache.org/jira/browse/MXNET-25
>             Project: Apache MXNet
>          Issue Type: Task
>          Components: MXNet Engine
>            Reporter: Chris Olivier
>            Priority: Major
>              Labels: performance, profliling
>
> In order to avoid using new/delete in performance-sensitive execution paths, 
> some profiling objects, such as ProfileOperator might be better to use 
> ObjectPool as their memory/object manager
> Ideally, this could occur by overloading the new/delete operators in a base 
> class (templated or nor), which would then call ObjectPool.New() and 
> ObjectPool.Delete()



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@mxnet.apache.org
For additional commands, e-mail: issues-h...@mxnet.apache.org

Reply via email to