Skip to content
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

edgeHub 1.1.5: UsePooledBuffers is undocumented #5568

Open
derSchtefan opened this issue Sep 23, 2021 · 2 comments
Open

edgeHub 1.1.5: UsePooledBuffers is undocumented #5568

derSchtefan opened this issue Sep 23, 2021 · 2 comments
Assignees
Labels
1.1.5 Targeted for 1.1.5 release bug Something isn't working customer-reported docs iotedge no-issue-activity

Comments

@derSchtefan
Copy link

derSchtefan commented Sep 23, 2021

Expected Behavior

The UsePooledBuffers should be documented somewhere, for instance https://docs.microsoft.com/en-us/azure/iot-edge/production-checklist?view=iotedge-2018-06&preserve-view=true

Current Behavior

UsePooledBuffers documentation is nowhere to be found. The production-readyness document at https://docs.microsoft.com/en-us/azure/iot-edge/production-checklist?view=iotedge-2018-06&preserve-view=true explains to set OptimizeForPerformance to false on constrained devices to disable the PooledByteBufferAllocator along with reduced memory requirement of RocksDb, but since 1.1.5 with commit 50027ff the undocumented flag UsePooledBuffers has been split out, making OptimizeForPerformance not switch them off, yet this flag is nowhere documented and also not referenced in the aforementioned document.

This leads to an uncertainty amongst users of "constrained" IoT devices if they can safely upgrade to 1.1.5

Runtime Versions

edgeHub 1.1.5

@varunpuranik
Copy link
Contributor

Thanks for catching this @derSchtefan. We will fix the documentation to include this flag as well.
Meanwhile, we recommending not setting this flag, and leaving it to its default value (false) for production scenarios.

@varunpuranik varunpuranik self-assigned this Sep 23, 2021
@varunpuranik varunpuranik added the bug Something isn't working label Sep 23, 2021
@github-actions
Copy link

This issue is being marked as stale because it has been open for 30 days with no activity.

@pmzara pmzara added 1.1.5 Targeted for 1.1.5 release docs labels Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.1.5 Targeted for 1.1.5 release bug Something isn't working customer-reported docs iotedge no-issue-activity
Projects
None yet
Development

No branches or pull requests

3 participants