-
Notifications
You must be signed in to change notification settings - Fork 1.4k
feat: Adding threshold for logging memory pool allocations #14437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Adding threshold for logging memory pool allocations #14437
Conversation
✅ Deploy Preview for meta-velox canceled.
|
|
This pull request was exported from Phabricator. Differential Revision: D79902261 |
Summary: I added threshold for logging memory pool allocations": facebookincubator/velox#14437 In this adding I'm adding corresponding session property to configure the threshold. Differential Revision: D80066283
…prestodb#25750) Summary: I added threshold for logging memory pool allocations": facebookincubator/velox#14437 In this adding I'm adding corresponding session property to configure the threshold. Differential Revision: D80066283
…shold_bytes (prestodb#25750) Summary: I added threshold for logging memory pool allocations": facebookincubator/velox#14437 In this adding I'm adding corresponding session property to configure the threshold. Differential Revision: D80066283
a870bcc to
02ab628
Compare
…or#14437) Summary: We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Differential Revision: D79902261
|
This pull request was exported from Phabricator. Differential Revision: D79902261 |
…or#14437) Summary: We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Differential Revision: D79902261
02ab628 to
1ffd416
Compare
|
This pull request was exported from Phabricator. Differential Revision: D79902261 |
…or#14437) Summary: We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Differential Revision: D79902261
1ffd416 to
8c721de
Compare
|
This pull request was exported from Phabricator. Differential Revision: D79902261 |
8c721de to
855f5ac
Compare
…or#14437) Summary: We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Differential Revision: D79902261
|
This pull request was exported from Phabricator. Differential Revision: D79902261 |
855f5ac to
c5937da
Compare
…or#14437) Summary: We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Differential Revision: D79902261
|
This pull request was exported from Phabricator. Differential Revision: D79902261 |
…or#14437) Summary: Pull Request resolved: facebookincubator#14437 We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Differential Revision: D79902261
c5937da to
7dbced0
Compare
…shold_bytes (prestodb#25750) Summary: I added threshold for logging memory pool allocations": facebookincubator/velox#14437 In this adding I'm adding corresponding session property to configure the threshold. Differential Revision: D80066283
7dbced0 to
1819d1c
Compare
|
This pull request was exported from Phabricator. Differential Revision: D79902261 |
|
This pull request has been merged in 255da1a. |
…shold_bytes (prestodb#25750) Summary: I added threshold for logging memory pool allocations": facebookincubator/velox#14437 In this adding I'm adding corresponding session property to configure the threshold. Differential Revision: D80066283
…shold_bytes (prestodb#25750) Summary: I added threshold for logging memory pool allocations": facebookincubator/velox#14437 In this adding I'm adding corresponding session property to configure the threshold. Differential Revision: D80066283
…shold_bytes (prestodb#25750) Summary: I added threshold for logging memory pool allocations": facebookincubator/velox#14437 In this adding I'm adding corresponding session property to configure the threshold. Reviewed By: tanjialiang Differential Revision: D80066283
…shold_bytes (prestodb#25750) Summary: I added threshold for logging memory pool allocations": facebookincubator/velox#14437 In this adding I'm adding corresponding session property to configure the threshold. Reviewed By: tanjialiang Differential Revision: D80066283
…shold_bytes (prestodb#25750) Summary: I added threshold for logging memory pool allocations": facebookincubator/velox#14437 In this adding I'm adding corresponding session property to configure the threshold. Reviewed By: tanjialiang Differential Revision: D80066283
…shold_bytes (prestodb#25750) Summary: I added threshold for logging memory pool allocations": facebookincubator/velox#14437 In this adding I'm adding corresponding session property to configure the threshold. Reviewed By: tanjialiang Differential Revision: D80066283
…shold_bytes (prestodb#25750) Summary: I added threshold for logging memory pool allocations": facebookincubator/velox#14437 In this adding I'm adding corresponding session property to configure the threshold. Reviewed By: tanjialiang Differential Revision: D80066283
…shold_bytes (prestodb#25750) Summary: I added threshold for logging memory pool allocations": facebookincubator/velox#14437 In this adding I'm adding corresponding session property to configure the threshold. Reviewed By: tanjialiang Differential Revision: D80066283
) Summary: I added threshold for logging memory pool allocations": facebookincubator/velox#14437 In this adding I'm adding corresponding session property to configure the threshold. Differential Revision: D80066283
…or#14437) Summary: Pull Request resolved: facebookincubator#14437 We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Reviewed By: tanjialiang Differential Revision: D79902261 fbshipit-source-id: 98dfc2ed25e45fa3a7881fdaf71743677d012173
…or#14437) Summary: Pull Request resolved: facebookincubator#14437 We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Reviewed By: tanjialiang Differential Revision: D79902261 fbshipit-source-id: 98dfc2ed25e45fa3a7881fdaf71743677d012173
…or#14437) Summary: Pull Request resolved: facebookincubator#14437 We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Reviewed By: tanjialiang Differential Revision: D79902261 fbshipit-source-id: 98dfc2ed25e45fa3a7881fdaf71743677d012173
…or#14437) Summary: Pull Request resolved: facebookincubator#14437 We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Reviewed By: tanjialiang Differential Revision: D79902261 fbshipit-source-id: 98dfc2ed25e45fa3a7881fdaf71743677d012173
…or#14437) Summary: Pull Request resolved: facebookincubator#14437 We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Reviewed By: tanjialiang Differential Revision: D79902261 fbshipit-source-id: 98dfc2ed25e45fa3a7881fdaf71743677d012173
…or#14437) Summary: Pull Request resolved: facebookincubator#14437 We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Reviewed By: tanjialiang Differential Revision: D79902261 fbshipit-source-id: 98dfc2ed25e45fa3a7881fdaf71743677d012173
…or#14437) Summary: Pull Request resolved: facebookincubator#14437 We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Reviewed By: tanjialiang Differential Revision: D79902261 fbshipit-source-id: 98dfc2ed25e45fa3a7881fdaf71743677d012173
…or#14437) Summary: Pull Request resolved: facebookincubator#14437 We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Reviewed By: tanjialiang Differential Revision: D79902261 fbshipit-source-id: 98dfc2ed25e45fa3a7881fdaf71743677d012173
…or#14437) Summary: Pull Request resolved: facebookincubator#14437 We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Reviewed By: tanjialiang Differential Revision: D79902261 fbshipit-source-id: 98dfc2ed25e45fa3a7881fdaf71743677d012173
…or#14437) Summary: Pull Request resolved: facebookincubator#14437 We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Reviewed By: tanjialiang Differential Revision: D79902261 fbshipit-source-id: 98dfc2ed25e45fa3a7881fdaf71743677d012173
…or#14437) Summary: Pull Request resolved: facebookincubator#14437 We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Reviewed By: tanjialiang Differential Revision: D79902261 fbshipit-source-id: 98dfc2ed25e45fa3a7881fdaf71743677d012173
…or#14437) Summary: Pull Request resolved: facebookincubator#14437 We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Reviewed By: tanjialiang Differential Revision: D79902261 fbshipit-source-id: 98dfc2ed25e45fa3a7881fdaf71743677d012173
…or#14437) Summary: Pull Request resolved: facebookincubator#14437 We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Reviewed By: tanjialiang Differential Revision: D79902261 fbshipit-source-id: 98dfc2ed25e45fa3a7881fdaf71743677d012173
…or#14437) Summary: Pull Request resolved: facebookincubator#14437 We have a leak check in memory pool the prints all current allocations along with call sites. In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now. Reviewed By: tanjialiang Differential Revision: D79902261 fbshipit-source-id: 98dfc2ed25e45fa3a7881fdaf71743677d012173
…stodb#25750) Summary: I added threshold for logging memory pool allocations": facebookincubator/velox#14437 In this adding I'm adding corresponding session property to configure the threshold. Differential Revision: D80066283
Summary:
We have a leak check in memory pool the prints all current allocations along with call sites.
In this diff I'm expanding that functionality and adding possibility to log that information once we reach configurable threshold. It's supposed to be used for debugging, when we want to know how exactly the memory has been used in particular memory pool. Adding this only for leaf nodes for now.
Differential Revision: D79902261
Test plan:
Example logs: