You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mxnet.apache.org by "Chris Olivier (JIRA)" <ji...@apache.org> on 2018/03/01 16:40:00 UTC
[jira] [Updated] (MXNET-25) Convert created profiling objects to
use ObjectPool
[ https://issues.apache.org/jira/browse/MXNET-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Olivier updated MXNET-25:
-------------------------------
Description:
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()
> 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
> Reporter: Chris Olivier
> Priority: Major
>
> 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-unsubscribe@mxnet.apache.org
For additional commands, e-mail: issues-help@mxnet.apache.org