-
Notifications
You must be signed in to change notification settings - Fork 300
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
HPCC-15582 Revert HPCC-15489 and give slave managers own cache #8676
Conversation
Signed-off-by: Jake Smith <jake.smith@lexisnexis.com>
https://track.hpccsystems.com/browse/HPCC-15582 |
@ghalliday - please review |
Automated Smoketest |
roxiemem::RoxieHeapFlags flags; | ||
AllocatorKey(IOutputMetaData *_meta, unsigned __int64 &_activityId, roxiemem::RoxieHeapFlags _flags) | ||
AllocatorKey(IOutputMetaData *_meta, unsigned &_activityId, roxiemem::RoxieHeapFlags _flags) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor: normally activityId wouldn't be a reference parameter
@jakesmith a few minor comments. I think the change will work. I'm not a great fan of passing in the array of slave allocators, but it is relatively clean, so no big objections. |
Signed-off-by: Jake Smith <jake.smith@lexisnexis.com>
An alternative I supposed would be to either have a :
which create the slaveManager with provided cache at the time. Or a :
.. i.e. used default globalRowManager cache, unless this was called to override. |
Automated Smoketest |
I'll merge as-is. We can possibly think about restructuring the parameters at a later date. |
Signed-off-by: Jake Smith jake.smith@lexisnexis.com