ocean
ocean copied to clipboard
[Integration][AWS-V3] Improve Memory Management On AWS-V3
User description
Description
What -
Why -
How -
Type of change
Please leave one option from the following and delete the rest:
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] New Integration (non-breaking change which adds a new integration)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] Non-breaking change (fix of existing functionality that will not change current behavior)
- [ ] Documentation (added/updated documentation)
All tests should be run against the port production environment(using a testing org).
Core testing checklist
- [ ] Integration able to create all default resources from scratch
- [ ] Resync finishes successfully
- [ ] Resync able to create entities
- [ ] Resync able to update entities
- [ ] Resync able to detect and delete entities
- [ ] Scheduled resync able to abort existing resync and start a new one
- [ ] Tested with at least 2 integrations from scratch
- [ ] Tested with Kafka and Polling event listeners
- [ ] Tested deletion of entities that don't pass the selector
Integration testing checklist
- [ ] Integration able to create all default resources from scratch
- [ ] Completed a full resync from a freshly installed integration and it completed successfully
- [ ] Resync able to create entities
- [ ] Resync able to update entities
- [ ] Resync able to detect and delete entities
- [ ] Resync finishes successfully
- [ ] If new resource kind is added or updated in the integration, add example raw data, mapping and expected result to the
examplesfolder in the integration directory. - [ ] If resource kind is updated, run the integration with the example data and check if the expected result is achieved
- [ ] If new resource kind is added or updated, validate that live-events for that resource are working as expected
- [ ] Docs PR link here
Preflight checklist
- [ ] Handled rate limiting
- [ ] Handled pagination
- [ ] Implemented the code in async
- [ ] Support Multi account
Screenshots
Include screenshots from your environment showing how the resources of the integration will look.
API Documentation
Provide links to the API documentation used for this integration.
PR Type
Bug fix
Description
-
Reduce concurrent region and account limits to prevent memory exhaustion
-
Replace Semaphore with BoundedSemaphore for proper resource cleanup
-
Add explicit garbage collection and resource deletion after processing
-
Reorder S3 bucket actions to optimize memory usage patterns
Diagram Walkthrough
flowchart LR
A["Memory Issues"] -->|Reduce Concurrency| B["_MAX_CONCURRENT_REGIONS: 10→5"]
A -->|Replace Semaphore| C["Semaphore→BoundedSemaphore"]
A -->|Explicit Cleanup| D["gc.collect() + del statements"]
A -->|Reorder Actions| E["S3 bucket action optimization"]
B --> F["Improved Memory Management"]
C --> F
D --> F
E --> F
File Walkthrough
| Relevant files | |||
|---|---|---|---|
| Enhancement |
| ||
| Bug fix |
|