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

Enhance Datumaro data format detect() to be memory-bounded and performant #1229

Merged
merged 2 commits into from
Dec 18, 2023

Conversation

vinnamkim
Copy link
Contributor

@vinnamkim vinnamkim commented Dec 14, 2023

Summary

  • Ticket no. 127136

How to test

Refer to #1224 for details on how we obtained the following results.

  1. Performance
  • Before
Duration for detecting Datumaro data format: 25784.5ms, format=datumaro
  • After
Duration for detecting Datumaro data format: 5966.8ms, format=datumaro
  1. Memory usage
  • Before
    before
  • After
    after

Checklist

  • I have added unit tests to cover my changes.​
  • I have added integration tests to cover my changes.​
  • I have added the description of my changes into CHANGELOG.​
  • I have updated the documentation accordingly

License

  • I submit my code changes under the same MIT License that covers the project.
    Feel free to contact the maintainers if that's a concern.
  • I have updated the license header for each file (see an example below).
# Copyright (C) 2023 Intel Corporation
#
# SPDX-License-Identifier: MIT

Signed-off-by: Kim, Vinnam <vinnam.kim@intel.com>
@vinnamkim vinnamkim marked this pull request as ready for review December 14, 2023 07:58
@vinnamkim vinnamkim requested review from a team as code owners December 14, 2023 07:58
@vinnamkim vinnamkim requested review from wonjuleee and removed request for a team December 14, 2023 07:58
@vinnamkim vinnamkim added this to the 1.6.0 milestone Dec 14, 2023
@vinnamkim vinnamkim added the ENHANCE Enhancement of existing features label Dec 14, 2023
Signed-off-by: Kim, Vinnam <vinnam.kim@intel.com>
Copy link

codecov bot commented Dec 14, 2023

Codecov Report

Attention: 6 lines in your changes are missing coverage. Please review.

Comparison is base (044b705) 80.44% compared to head (7a6a1a2) 80.45%.

Files Patch % Lines
.../plugins/data_formats/segment_anything/importer.py 68.42% 3 Missing and 3 partials ⚠️
Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1229   +/-   ##
========================================
  Coverage    80.44%   80.45%           
========================================
  Files          269      269           
  Lines        29919    29944   +25     
  Branches      5851     5853    +2     
========================================
+ Hits         24069    24090   +21     
- Misses        4487     4488    +1     
- Partials      1363     1366    +3     
Flag Coverage Δ
macos-11_Python-3.8 79.10% <81.81%> (-0.01%) ⬇️
ubuntu-20.04_Python-3.8 80.44% <81.81%> (-0.01%) ⬇️
windows-2022_Python-3.8 80.41% <78.78%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@wonjuleee wonjuleee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@vinnamkim vinnamkim merged commit 3a5f138 into openvinotoolkit:develop Dec 18, 2023
7 checks passed
vinnamkim added a commit to vinnamkim/datumaro that referenced this pull request Jan 9, 2024
…mant (openvinotoolkit#1229)

- Ticket no. 127136

Refer to openvinotoolkit#1224 for
details on how we obtained the following results.

1. Performance

- Before

```console
Duration for detecting Datumaro data format: 25784.5ms, format=datumaro
```
- After

```console
Duration for detecting Datumaro data format: 5966.8ms, format=datumaro
```

2. Memory usage
- Before

![before](https://github.com/openvinotoolkit/datumaro/assets/26541465/9f6432f7-108d-4d9f-a535-f954bfd55f02)
- After

![after](https://github.com/openvinotoolkit/datumaro/assets/26541465/8ff7a1a4-6106-46cc-9f16-74a4979b8a3b)

<!-- Put an 'x' in all the boxes that apply -->
- [ ] I have added unit tests to cover my changes.​
- [ ] I have added integration tests to cover my changes.​
- [x] I have added the description of my changes into
[CHANGELOG](https://github.com/openvinotoolkit/datumaro/blob/develop/CHANGELOG.md).​
- [ ] I have updated the
[documentation](https://github.com/openvinotoolkit/datumaro/tree/develop/docs)
accordingly

- [x] I submit _my code changes_ under the same [MIT
License](https://github.com/openvinotoolkit/datumaro/blob/develop/LICENSE)
that covers the project.
  Feel free to contact the maintainers if that's a concern.
- [x] I have updated the license header for each file (see an example
below).

```python
```

---------

Signed-off-by: Kim, Vinnam <vinnam.kim@intel.com>
vinnamkim added a commit that referenced this pull request Jan 11, 2024
### Summary

- Ticket no 128951
- Apply #1224 and #1229 changes to the releases/1.5.0 branch

### How to test
Already tested in the previous PRs.

### Checklist
<!-- Put an 'x' in all the boxes that apply -->
- [ ] I have added unit tests to cover my changes.​
- [ ] I have added integration tests to cover my changes.​
- [ ] I have added the description of my changes into
[CHANGELOG](https://github.com/openvinotoolkit/datumaro/blob/develop/CHANGELOG.md).​
- [ ] I have updated the
[documentation](https://github.com/openvinotoolkit/datumaro/tree/develop/docs)
accordingly

### License

- [ ] I submit _my code changes_ under the same [MIT
License](https://github.com/openvinotoolkit/datumaro/blob/develop/LICENSE)
that covers the project.
  Feel free to contact the maintainers if that's a concern.
- [ ] I have updated the license header for each file (see an example
below).

```python
# Copyright (C) 2023 Intel Corporation
#
# SPDX-License-Identifier: MIT
```

---------

Signed-off-by: Kim, Vinnam <vinnam.kim@intel.com>
@yunchu yunchu modified the milestones: 1.6.0, 2.0.0 Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ENHANCE Enhancement of existing features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants